-
Notifications
You must be signed in to change notification settings - Fork 80
Support Cadence import aliasing in Dependency Manager #2192
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Dependency Review✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.Scanned FilesNone |
Codecov Report❌ Patch coverage is
📢 Thoughts on this report? Let us know! |
| for _, imp := range imports { | ||
| importContractName := imp.Imports[0].Identifier.Identifier | ||
|
|
||
| actualContractName := imp.Imports[0].Identifier.Identifier |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
what happens if imports > 0
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Each address import statement imports exactly one contract, so imp.Imports always has one element. The outer loop handles multiple import statements
- Changed --alias flag to --name flag for better clarity - Updated all references from Alias to Name in DependencyInstaller - Updated documentation and examples to use --name instead of --alias - Updated tests to reflect the new flag name
Add name flag for aliasing
Closes #???
Description
For contributor use:
masterbranchFiles changedin the Github PR explorer