336 ROR search field doesn't always populate ROR URL #362
Conversation
This file contains 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
…uery. Switch to using exact match in query so that spaces are handled correctly
|
Visit the preview URL for this PR (updated for commit de22f16): https://cioos-metadata-form-dev--pr362-336-ror-search-field-izlw38m2.web.app (expires Fri, 12 Jul 2024 17:54:50 GMT) 🔥 via Firebase Hosting GitHub Action 🌎 Sign: 3ac34821b6d06862dcbab3b63feae62f4121aa78 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
fix #336
populate ror immedeitly if only one result is returned. use exact matching qhen searching for organizations so that spaces are handled correclty