You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If it's possible to have programatically-defined columns, that should be documented.
I don't think it is, and so far I haven't been able to achieve it anyway, so I am not sure if it's even possible, but if I have a couple of pointers I'll be happy to write it up in the documentation.
Example use case: A child has a height. But Child.height alone perhaps isn't adequate, because children grow, so we might also have a model for Year, and a through model that allows us to record a Child's height for each Year. In the table we'd therefore want a column for each Year:
It's possible to acquire both the Year column headings and data by looping over attributes in the template, but that negates much of the convenience that has been afforded.
The text was updated successfully, but these errors were encountered:
If it's possible to have programatically-defined columns, that should be documented.
I don't think it is, and so far I haven't been able to achieve it anyway, so I am not sure if it's even possible, but if I have a couple of pointers I'll be happy to write it up in the documentation.
Example use case: A child has a height. But
Child.height
alone perhaps isn't adequate, because children grow, so we might also have a model forYear
, and a through model that allows us to record aChild
's height for eachYear
. In the table we'd therefore want a column for eachYear
:It's possible to acquire both the
Year
column headings and data by looping over attributes in the template, but that negates much of the convenience that has been afforded.The text was updated successfully, but these errors were encountered: