Closed estebanz01 closed 6 days ago
This looks to be more of an issue with Rails generator actions (which this library uses) and not unique to the beta release, specifically #gem
- which doesn't account for dupes in the Gemfile before adding
📝 this does the same thing when running rails_admin:install
with Sprockets (the installer adds sassc-rails
even if it's already in the Gemfile).
Is there any update on this?
is there a solution to the above problem?
Just remove the line if redundant.
Describe the bug Hello! I'm testing rails admin 3.1.0 beta and when I run the installer, the Gemfile ended up with two entries for
cssbundling-rails
, the one that I had already and the one rails admin installer adds.Reproduction steps with a configured
jsbundling-rails
withwebpack
andcssbundling-rails
withsass
gems:bundle add jsbundling-rails
bundle add cssbundling-rails
bundle exec rails javascript:install:webpack
bundle exec rails css:install:sass
bundle exec rails generate rails_admin:install
Expected behavior It should install without errors and
bundle install
should work properly.Additional context
rails
version: 7.0.3 created withbundle exec rails new --minimal
rails_admin
version: 3.1.0.betarails_admin
npm package version: 3.1.0.beta