feat: add persistent metadata map to claims#498
Merged
WiIIiam278 merged 2 commits intoJul 7, 2026
Merged
Conversation
WiIIiam278
reviewed
Jul 7, 2026
Contributor
Author
For most use cases; I don't think the child claim would need the metadata but if it did it could just use |
WiIIiam278
approved these changes
Jul 7, 2026
Owner
|
Thank you for contributing to HuskClaims! |
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
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.
Summary
Adds a per-claim metadata store so third-party plugins can attach persistent key-value data directly to claims.
Changes
metadata(Map<String, String>) toClaimgetClaimMetadata()andsetClaimMetadata()toHuskClaimsAPI