UIPQB-128: Invalid fields handling > Errors when query includes a deleted custom field #193
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
…eted custom field
vashjs
approved these changes
Dec 3, 2024
mweaver-ebsco
approved these changes
Dec 3, 2024
|
zburke
approved these changes
Dec 3, 2024
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.
https://folio-org.atlassian.net/browse/UIPQB-128
Here, we added a case of parsing a
mongoquery with default values in dropdowns because custom fields used for the query can be deleted. By default, if the field is deleted, we will render the default unselected value inside the query builder to prevent the plugin from crashing.Screen.Recording.2024-12-03.at.15.15.04.mov