Make all state autocomplete options visible in occurrenceeditor #1718
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.
Before:
After:
Edge case with "USA":
Issue #1647:
@themerekat , the autocomplete feature for state/province works in a way that it grabs the parent value from country input field and checks for the possible geoterms within "geographicthesaurus" table where this country value ID == parentID. I assumed that you wanted the state/province input to show all possible options from our "geographicthesaurus" table if the country input is invalid (not in our "geographicthesaurus" table). Is that correct?
The issue with "USA":
Currently "USA" country input will be considered as valid which could be fixed but I'm not sure why we even need a separate value for United States in table as "USA" and not have a single value "United States" or "United States/USA" in the first place. This seems like a duplicate to me.
Changes Made:
Pull Request Checklist:
Pre-Approval
master
branch and squash and merged back into themaster
branch.Development
branch, NOTmaster
Post-Approval
Development
branch, remember to use the squash & merge optionDevelopment
branch into the master branch, remember to use the merge optionmaster
branch, a subsequent PR frommaster
intoDevelopment
should be made merge option (i.e., no squash).Development
branch before a tagged release (i.e., before an imminent merge into the master branch), make sure to notify the team and lock theDevelopment
branch to prevent accidental merges while QA takes place. Follow the release protocol here.Thanks for contributing and keeping it clean!