Publish latest version on Rubygems

[scarroll32]

4.1.3 is published, but gem is at 4.5

https://rubygems.org/gems/cells/versions/4.1.3

[ramontayag]

@apotonick? :)

[apotonick]

I think this is a misunderstanding here in the core team, not sure why there's a pointless 4.5.0 version? 🤔 💭

[apotonick]

@ramontayag !!! 😍

[scarroll32]

There seem to be a few things added since 4.1.7 was published .... https://github.com/trailblazer/cells/commits/master

[marnen]

We're coming up on 3 years since the last gem release. Can we have a release with the current code?

[richard-kramer]

@apotonick Is there any update to this? Just stumbled upon a bug which was already fixed in 2018, but I cannot really use it in my gem, because this version is not published to rubygems. It works by manually defining the gem referencing the github repo inside the gemfile, but thats not a great solution 5 years later.

[apotonick]

Hey @richard-kramer let me finally have a look into that, unless @seuros sheds some light onto this?

Sorry for the delay, with ViewComponent it's kind of pointless for us...

[richard-kramer]

Thanks. And I understand that, ViewComponent essentially does the same. But it does not play well with non-rails projects (which cells does) and we also don't want to switch everything to ViewComponent just because. So because there already are fixes for some things with cells, I would greatly appreciate, if they become more usable with a new gem release 😁.

[apotonick]

@richard-kramer Out of pure curiosity, what is your underlying framework?

[richard-kramer]

Cells is used in a standalone Gem. But it will end up in rails. We do want to decouple from rails as best as possible, nonetheless. And that's harder with ViewModel.