Linus Marton

I don't know :) There are probably a lot of cases where you'd want to pass options. Especially if you create a more general filter. Example: ```ruby FILTERS = [...

Hmm I don't think we should add it by default... At least not until we've tried it a bit more ourselves first :D Perhaps it can just be documented in...

Sure, but everyone who uses engines already will be confused that they _don't_ have to require? :) That's probably less people though. Maybe we should nudge people in the right...

I meant if some gems do something even weirder. gem: `foo-bar-baz` File to require is `lib/foo/bar_baz.rb` That would not be caught by the require above. It would blow up in...

Yep. Perhaps that is a better idea. Any other drawbacks we can think of other than “gemification” of an engine?

Just a note, both of the Godmin examples above can be done without overriding views. The symbols passed to `attrs_for_index` are called as methods on the resource so you can...

Also, doesn't it already work with single association if it defines a `to_s` method?

Yes we removed the automatic linking of associations but they should print ok though? :)

Not sure I understand what you mean. Do you mean having a separate `sort_order` column and use `prepend_child` or `prepend_sibling` when creating a comment which is nested?

Seems nice :) And then I'd get all my comments correctly with one query? Btw, is it possible to use pagination with closure_tree?