Refs #38925 - make host package transience optional#1016
Merged
Conversation
Member
Author
|
Thanks @chris1984 ! I just wanna see @qcjames53 's opinion before merging since I'm modifying his recent change |
qcjames53
approved these changes
Dec 3, 2025
Member
qcjames53
left a comment
qcjames53
left a comment
There was a problem hiding this comment.
I think this is a great change. Thanks, Ian!
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
3 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.
I'm proposing that we add package transience to the optional fields and add it to the "ALL" field set. For now, most host packages will have no package transience data, so the majority of users will be looking at a completely blank column.