Skip to content
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

fix: reorganise charmcraft.yaml preprocessing #1622

Merged
merged 3 commits into from
Apr 3, 2024

Conversation

lengau
Copy link
Collaborator

@lengau lengau commented Mar 26, 2024

This makes a few related changes:

  1. Extensions are applied on the rawest charmcraft.yaml data we have
  2. Charms with a "bases" key (not just bundles) get a default part.
  3. Always expect a dictionary for parts.

This makes a few related changes:

1. Extensions are applied on the rawest charmcraft.yaml data we have
2. Charms with a "bases" key (not just bundles) get a default part.
3. Always expect a dictionary for parts.
@lengau lengau force-pushed the CRAFT-2645/no-parts-side-effect branch from f3bf38d to 862d307 Compare March 26, 2024 20:43
@lengau lengau requested review from tigarmo, mr-cal and syu-w April 1, 2024 17:57
@lengau lengau merged commit 7ce4182 into main Apr 3, 2024
14 of 15 checks passed
@lengau lengau deleted the CRAFT-2645/no-parts-side-effect branch April 3, 2024 21:31
tonyandrewmeyer pushed a commit to tonyandrewmeyer/charmcraft that referenced this pull request Apr 4, 2024
This makes a few related changes:

1. Extensions are applied on the rawest charmcraft.yaml data we have
2. Charms with a "bases" key (not just bundles) get a default part.
3. Always expect a dictionary for parts.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants