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
Generic InitCommand should be created, so all the crafts can use it, that allows:
specifying name as an option and project_dir as a positional argument (the way cargo / uv works)
use Jinja2 for templates
support profiles e.g. by searching templates for subdirectories and listing them as options
by default it will allow to be run in non-empty directory, as long as it creates only new files (no-overrides). This behavior may be overwritten (opt-out), so charmcraft will be able to error-out in non-empty directory
Why it needs to get done
Currently all the applications have a separate way of handling init.
We should create a generic version, that everyone can use.
It will enable create specific profiles in snapcraft, make our codebase smaller and it will be easier to maintain in the single place.
The text was updated successfully, but these errors were encountered:
What needs to get done
Generic InitCommand should be created, so all the crafts can use it, that allows:
name
as an option andproject_dir
as a positional argument (the waycargo
/uv
works)templates
for subdirectories and listing them as optionsWhy it needs to get done
Currently all the applications have a separate way of handling
init
.We should create a generic version, that everyone can use.
It will enable create specific profiles in snapcraft, make our codebase smaller and it will be easier to maintain in the single place.
The text was updated successfully, but these errors were encountered: