DRYD-2144 Authority Fields > Predictive Search Result Messaging - #28
Merged
Conversation
…, displayed when any source returns a truncated result list;
mikejritter
approved these changes
Jul 24, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What does this do?
Adds a new
formatNarrowResultsMessageprop to AutocompleteInput, and shows that message ("Continue typing to narrow results" by default) in the dropdown header whenever any of the field's sources returns a truncated result list. A source is considered truncated when the server reports more matches than it returned, or when it returned a full page of results. The search service caps totalItems at the page size (https://collectionspace.atlassian.net/browse/DRYD-2157), so a full page is the only reliable truncation signal. For multi-vocabulary sources, each vocabulary is checked independently. One truncated vocabulary is enough to show the message.Why are we doing this? (with JIRA link)
https://collectionspace.atlassian.net/browse/DRYD-2144. The message that states: “40 matching terms found” is confusing because this actually translates to at least 40 and not exactly 40.
How should this be tested? Do these changes have associated tests?
Tests have been added. For manual testing please follow the steps: collectionspace/cspace-ui.js#367
Dependencies for merging? Releasing to production?
It should be released/published along the collectionspace/cspace-ui.js#367.
Has the application documentation been updated for these changes?
Changelog has been updated
Did someone actually run this code to verify it works?
@spirosdi ran it locally