What problem does this solve?
The generate command currently refuses to scaffold into directories that already contain files.
While this is a sensible default, there are valid cases where users intentionally want to generate files into an existing directory.
Proposed solution
Add a -f, --force flag that allows generation inside non-empty directories.
When the flag is used:
- Display a warning indicating that files may be overwritten.
- Continue with generation instead of aborting.
Example:
scaffinity generate blueprint.json --force
Alternatives considered
Users currently have to create a new directory or manually move files after generation, which adds unnecessary steps.
Would you be willing to open a PR for this?
What problem does this solve?
The
generatecommand currently refuses to scaffold into directories that already contain files.While this is a sensible default, there are valid cases where users intentionally want to generate files into an existing directory.
Proposed solution
Add a
-f, --forceflag that allows generation inside non-empty directories.When the flag is used:
Example:
Alternatives considered
Users currently have to create a new directory or manually move files after generation, which adds unnecessary steps.
Would you be willing to open a PR for this?