Cells 5: Removal of Cell::Concept

[apotonick]

Problem

The differentiation between ViewModel and Concept is not only confusing, the latter also implements some conventions that are not in line with the Trailblazer conventions (which is why I originally introduced Concept).

Solution

Per default, pass a constant to cell.

cell(Post::Cell, ..)

The #cell helper can be configured globally (on the ViewModel class level) to constantize and what not. This assumes that applications either use TRB-style concept cells or suffix cells.

ViewModel.constantize_name! # just an example.

This will allow having one helper cell, one base class ViewModel and the view finding implemented using different resolvers.

[thedanielhanke]

👍 i prefer a more explicit writing anyway. :foo is more magical than Foo::Cell.

[TrevorHinesley]

@apotonick if I'm starting a new project with Cells in Rails, should I use concept or cell? If I'm reading this right, concept syntax will be gone in V5.

[apotonick]

https://github.com/trailblazer/trailblazer-cells is gonna be the preferred, canonical way. I love it.

[TrevorHinesley]

Totally, i just mean is the actual concept helper going to be no more, so that cell is used everywhere? Because in trailblazer-cells I can still use either

[apotonick]

In Cells 5, cell and concept will be identical.

[thedanielhanke]

then why keeping it?

[apotonick]

In Cells 5, it'll be gone! In 4.1, the old-school RailsWayCell style is still supported, but I hate it a lot! 😆 🚀

[thedanielhanke]

new major is always a good time to kick out the known devils.
if that hurts, add a convenience-wrapper, but dont bother too much about compatilibity, fame money and bi***es, its still ruby ;)

[yjukaku]

Just wanted to point out, the trailblazer site still references the concept() method, which was a little confusing to me until I saw this issue. 👍

http://trailblazer.to/gems/cells/

[apotonick]

Make sure to only use Trailblazer::Cell, it's the API of the upcoming Cells 5 that drops all the former versions.