Custom forms fixes #361
Merged
Custom forms fixes #361
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
…han one pair of type selectors and autocomplete field used
chenejac
approved these changes
Jan 24, 2023
ghost
pushed a commit
that referenced
this pull request
Feb 23, 2023
* added safety check * Prevent failing autocomplete field with type selectors in case more than one pair of type selectors and autocomplete field used --------- Co-authored-by: Georgy Litvinov <georgy.litvinov@tib.eu>
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.
What does this pull request do?
Adds fixes for shared js files used in custom entry forms
What's new?
Added safety check in capitalize function
Fixed broken type selector + autocomplete field if more than one type selector appears on the page.
Interested parties
@VIVO-project/vivo-committers @chenejac @brianjlowe