You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
The latest charm development style is to use a single
charmcraft.yaml
file instead of multiple individual files (e.g.,metadata.yaml
,config.yaml
, oractions.yaml
).The extension should support this style while keeping the current behavior for backward-compatibility. This also affects the way we show
config.yaml
oractions.yaml
in the sidebar tree. We need to keep things separated in the tree (i.e., not nesting individual actions/configs under thecharmcraft.yaml
node), but we need to change the title of the node toActions
orConfigs
when they're defined in thecharmcraft.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.The text was updated successfully, but these errors were encountered: