Lineage: add "restricted" property #1922
Merged
Conversation
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
This was referenced Jan 6, 2026
labkey-alan
approved these changes
Jan 6, 2026
Contributor
labkey-alan
left a comment
labkey-alan
left a comment
There was a problem hiding this comment.
Looks good. Glad to see these components get converted to FC.
aneek016
approved these changes
Jan 7, 2026
labkey-nicka
force-pushed
the
fb_lineage_441
branch
from
524ac10 to
4498219
Compare
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.
Rationale
See #441 for more details.
Related Pull Requests
Changes
restrictedprop on lineage nodes when displaying in lineage graph