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

Support charmcraft.yaml as single configuration file #30

Open
babakks opened this issue Apr 29, 2024 · 1 comment
Open

Support charmcraft.yaml as single configuration file #30

babakks opened this issue Apr 29, 2024 · 1 comment

Comments

@babakks
Copy link
Owner

babakks commented Apr 29, 2024

The latest charm development style is to use a single charmcraft.yaml file instead of multiple individual files (e.g., metadata.yaml, config.yaml, or actions.yaml).

The extension should support this style while keeping the current behavior for backward-compatibility. This also affects the way we show config.yaml or actions.yaml in the sidebar tree. We need to keep things separated in the tree (i.e., not nesting individual actions/configs under the charmcraft.yaml node), but we need to change the title of the node to Actions or Configs when they're defined in the charmcraft.yaml file.

Also, a warning diagnostic message should be displayed on YAML files to hint users to use a single charmcraft.yaml file. In addition to that, if a node is defined in more than one YAML file, a diagnostics message should complain about it.

@babakks babakks converted this from a draft issue Apr 29, 2024
@babakks babakks moved this from Todo to In Progress in vscode-juju-charmcraft-ide Apr 29, 2024
@Thanhphan1147
Copy link

+1. Looking forward to this feature!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: In Progress
Development

When branches are created from issues, their pull requests are automatically linked.

2 participants