- Issue created by @RoSk0
Composer scaffolding plugin is an awesome tool, but there is a space for improvement.
We use this plugin to scaffold base configuration for Drupal and other project components, but at all times we commit scaffolded configuration. Once initially scaffolded it becomes part of the project. All packages that scaffolds config are configured to avoid ignoring in Git and avoid overriding.
This approach requires more manual work to keep an eye on updates in scaffolds, but avoids surprises that automated scaffolding could bring. Focus on stability and predictability.
What I would like to see possible is the ability to call composer drupal:scaffold --force - which would tell plugin to ignore configured in the packages "overwrite": false rules and override already scaffolded files. With this new option we are not changing default behaviour , but it gives a user more control and simplifies the process of updating scaffolded files - rather then checking every scaffolded file one by one, I could call composer drupal:scaffold --force and use standard IDE tools or git diff to see what changed , what I should bring in or revert.