chore: enforce consistency between AccountComponentMetadata names and the component library paths#2593
Draft
PhilippGackstatter wants to merge 3 commits intonextfrom
Draft
chore: enforce consistency between AccountComponentMetadata names and the component library paths#2593PhilippGackstatter wants to merge 3 commits intonextfrom
AccountComponentMetadata names and the component library paths#2593PhilippGackstatter wants to merge 3 commits intonextfrom
Conversation
Contributor
Author
|
Putting this back into draft until we've made a decision in #2599. |
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.
Implements the missing piece from #2399:
AccountComponentMetadatanames and the account component's library path.agglayer::componentsanalogous tomiden::standards::componentsand how it was done in feat(standards): prefix account components with miden::standards namespace #2400.For now
AccountComponent::newenforces that the component name is a valid path, though I think we should add a thinAccountComponentName(String)wrapper that enforces this earlier, as a next step.