Issue 1472: Update check for allowing a field to be required to exclude or include aliquots depending on field derivation scope - #7954
Merged
Conversation
…de or include aliquots depending on field derivation scope
cnathe
removed their request for review
August 20, 2026 19:15
XingY
approved these changes
Aug 20, 2026
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
Issue 1472 The check for whether we can make a field on a sample type required or not needs to account for whether the field is separately editable for aliquots or not.
Related Pull Requests
Changes
SampleTypeDomainKind::hasNullValuesto account for the derivationScope of the field.