v3.6.0 allows Slim 5.0.0, which has a major issue with Rails (fixed on slim main but unreleased)

[tagliala]

v3.6.0 allows Slim 5.0.0, which has a major issue with Rails (fixed on slim main but unreleased)

[januszm]

I'll release 3.6.1 now with this fix in gemspec

[apannetrat]

Same problem here. Even running rails c after an upgrade to 3.6.0 gives:

.rvm/gems/ruby-2.7.6/gems/slim-5.0.0/lib/slim/railtie.rb:2:in `<module:Slim>': uninitialized constant Slim::Rails::Railtie (NameError)

[tagliala]

Ah sorry,

the braking change is related to Slim 5.0, which is being update together with 3.6.0

/Users/geremia/.rvm/gems/ruby-3.2.0/gems/slim-5.0.0/lib/slim/railtie.rb:2:in `<module:Slim>': uninitialized constant Slim::Rails::Railtie (NameError)

  class Railtie < Rails::Railtie

I'm leaving this open, but feel free to close or move to the proper repo

[mkhairi]

slim-template/slim#904

[januszm]

It's unfortunately a result of #185 which apparently wasn't fully tested with Rails and SLIM 5. We can yank 3.6.0 and release proper support for SLIM 5 when SLIM is fixed, as 3.6.1. A quick workaround for apps, until slim 5.0.1+ is released, is to lock slim in Gemfile to:

gem "slim", "!= 5.0.0", "< 6.0"

Personally, I'd prefer to wait until SLIM is resolved rather than yank this (because nothing is really wrong with this release).

[tagliala]

We can yank 3.6.0

Hi, I know that yanking is not ideal, but I was about to suggesting the same thing

Should a potential 3.6.1 add != 5.0.0 to the slim version constraints even after release of 5.0.1?

[tagliala]

Thanks, closing as fixed in 3.6.1