Add BRF record discovery - #72
Merged
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Users previously needed to know a QBS record ID or canonical identity before using quarry-brf-inspect. This PR adds standalone record discovery:
Minimal QBS output:
Reflective QBS output:
The numeric value can be copied to
--record-id; the canonical identity can be copied to--record-name. Reflective QBS additionally shows the optional display name. Minimal QBS is sufficient for discovery. All records in the QBS image are listed in validated record-table order; QBS has no root-record concept.The public
quarry_qbs_record_identity(...)API returns the mandatory canonical identity as a non-owning string view, so the CLI does not decode private QBS layout.No QBS or BRF format changes occurred. Compatibility epochs and formats remain unchanged.