Replies: 1 comment
-
|
If I understand right, yes, I can see how this is an issue. Thankfully though it's been resolved by removing the Columns component entirely for v4 which is coming soon. You shouldn't have an issue anymore with that release going forward. Thank you. I've removed many builder methods so you should have less conflicts. For example, we declared our site header and footer components as |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
I'm using:
I know
rowsandcolumnsis NOT documented, but it's pretty useful, especially with decorators where the show.rows and index.columns only define what to show and decorators define how to show it (I'm using mine ArbreDecorator).To make
columnswork - I had to do:Now the question arises, is it worth documenting show.rows/index.columns and the trick to make columns work.
Going a step further could you consider extracting
ActiveAdmin::Views::Columnsto separate gem so it does not have to disabled but rather included with a note it affects index.columns behavior?Optionally the
Arbre::Element::BuilderMethods.columnsmethod could detect if it's first (and second?) argument is a symbol and act asActiveAdmin::Views::TableFor.columnsotherwise act asActiveAdmin::Views::Columns.I can help out with any changes needed :)
WDYT?
Beta Was this translation helpful? Give feedback.
All reactions