-
Notifications
You must be signed in to change notification settings - Fork 2
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
feat: multi-base support for charm build plans #81
Conversation
Signed-off-by: Callahan Kovacs <callahankovacs@gmail.com>
065e015
to
d8d3d7b
Compare
- rename variables - code simplifications - clarify doc strings Signed-off-by: Callahan Kovacs <callahankovacs@gmail.com>
Signed-off-by: Callahan Kovacs <callahankovacs@gmail.com>
Signed-off-by: Callahan Kovacs <callahankovacs@gmail.com>
In addition to the PR feedback, I switched to So now, you can't declare the base in the platform name and declare
|
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.
Nice! Thanks
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.
Thank you. This is now easier to understand, but be prepared for a bad score in cyclomatic analysis (which may require a future refactoring).
Thanks for the reviews, I'm going to leave this for another day or two in case I have any changes to make when consuming it in craft-application. |
Following Claudio's suggestion so we are slightly less tied to the arg names. Signed-off-by: Callahan Kovacs <callahankovacs@gmail.com>
make lint && make test
?Adds multi-base support for charm build plans.
Documentation will be added in another PR (#70).
Issues I found into when working on this task:
build-on
andbuild-for
#80Fixes #73
(CRAFT-3721) (the branch name has the wrong number)