test setRequired()#2937
Merged
labkey-matthewb merged 2 commits intorelease26.3-SNAPSHOTfrom Apr 7, 2026
Merged
Conversation
XingY
approved these changes
Apr 6, 2026
| // insert a row with a NULL value and NON-NULL value | ||
| Map<String, String> row = new HashMap<>(); | ||
| row.put(fieldA, "not null"); | ||
| row.put(fieldB, ""); |
Contributor
There was a problem hiding this comment.
Should there be a fieldC, that has a mixed value of empty and not empty, that also cannot be set to required?
Contributor
Author
There was a problem hiding this comment.
Adding a second row to cover that makes sense.
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.
Rationale
Test that field (non-MVTC) can't be set to required if null is present
regression test for change in LabKey/platform#7549
Related Pull Requests
-
Changes