Nick Sutterer
Nick Sutterer
@richard-kramer Out of pure curiosity, what is your underlying framework?
The problem is Reform 2.2.3, and not Cells. On Mon, Jan 30, 2017 at 3:53 AM, wintersolutions wrote: > I updated cells from 4.1.5 to version 4.1.6. When I run...
You can now upgrade to Reform 2.2.4, which doesn't use `uber` anymore.
Wow, I love this "using the model part" idea - I never thought of this! It shouldn't be hard to implement. We could simply catch the block and evaluate it...
If you just want to have different views for `show` simply derive an empty cell and drop the overriding view into `app/cells/linked_cell/show.haml`. ``` ruby class LinkedCell < AvatarCell end ```...
You can always render another state (method+view) using ``` ruby render :state => :show ``` or render another view (eh, view only) with ``` ruby render :view => :show ```
Ah, now I understand you. You want to extend the view with the "super" view. One first step would be introducing a new state. ``` ruby class LinkedCell < AvatarCell...
I played around with this a bit, I can see some new feature in cells similar to the one I proposed above. However, no urgent need to fix this right...
Also, I'd love to have a consistent API differing from Rails. ``` ruby render :view => "state" # render cell's view or inherit. render :view => "some_ascendent/state" # render inherited...
Try out the `:file` thing, it will work for you. What do you think of the proposed API with `:view`? Yeeaaah, 2.0!!!! :+1: