Conversation
|
Hey @arlando Thanks for the contribution 👏 I like the look of this. Let me get my head round the compatability issues with Rails < 6 and give you a better response as soon as I can. |
|
@arlando I played around with this a bit at the weekend but ran out of time. It might be that to support Rails 6 we have to drop support for some earlier versions of Rails and Ruby. It would be good to mimimise that as much as possible. Worst case, we have a new major version of this gem that only supports Rails 6 but I'd like to avoid that if possible. |
|
@billhorsman I'd like to avoid that too. Rails 6 changed the arity of the In Rails 6 the ruby wise, Rails 6 depends on versions |
|
@arlando I think your arity checks are fine, it's just the gem dependencies that worry me — as can be seen in the Travis test results. |
|
@billhorsman I'm new to this 😄 so there may be a smarter way of handling this. I will look into this more soon. |
Hi @billhorsman
I am working on having this library support Rails 6. I ran into a few regressions with the
inline-styles-mailergem against Rails 6. I've tried to add support while maintaining backwards compatibility as much as possible.In Rails 6 the
_layoutmethod's arity has changed. Therender_to_stringmethod when used with a:fileargument now requirements an absolute path to the file.On another note I believe the
sass-rubylibrary has been deprecated and upgrading to higher versions ofsass-railsnow depends onsassc-rubylibrary see: https://github.com/rails/sass-rails/releases/tag/v6.0.0. This library changes the name space ofSasstoSassCand there may not be sass feature rendering parity with previousSassversion see: http://sass-compatibility.github.io/. Hence, I made a lock of thesass-railsversion to~> 5.0.8to avoid potential breaking changes. I'd recommended doing a version bump when upgrading that just to be extra cautious.