bin/dev file collision, could it be prevented ?
bdavidxyz opened this issue · comments
David Boureau commented
Use case : create a new rails application
rails -v
7.1.2
rails new theapp --force --database=postgresql -j=esbuild -c=tailwind --skip-docker
Will result, despite the "force" option, into an interrupt :
rails css:install:tailwind
apply /home/david/.rbenv/versions/3.2.2/lib/ruby/gems/3.2.0/gems/cssbundling-rails-1.3.3/lib/install/install.rb
(...)
append Procfile.dev
Add bin/dev to start foreman
conflict bin/dev
Overwrite /home/david/workspace/railsback/flow/theapp/bin/dev? (enter "h" for help) [Ynaqdhm] a
Not a big deal for a simple "rails new" command, but still annoying in many scenario when you have to generate rails skeleton (template) apps, interrupting the build flow.
David Boureau commented
One possible hack is
echo "Y" | rails new theapp --force --database=postgresql -j=esbuild -c=tailwind --skip-docker
David Heinemeier Hansson commented
Fixed in Supported in 1.4.0.