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
Column definitions were put into JS land, because Ember and Handlebars lacked some important features regarding flexibility and composability. But the landscape is slowly shifting towards a shiny new future with one major advancement being the fantasticNamed Blocks RFC 226 by @machty. ☀️ ✨
The ultimate goal is to remove the need for the columns array and instead define the columns in the template. Maybe we'll also be able to remove the need for Table objects.
This issue is meant to serve as a brain dump and constant reminder. If you have ideas, wishes, questions or anything else related to this, please do add a comment! 😊
The text was updated successfully, but these errors were encountered:
It's a good idea, but I would imagine the feature needs to exist side-by-side with data-driven column definition. How else can you persist the column reordering?
Column definitions were put into JS land, because Ember and Handlebars lacked some important features regarding flexibility and composability. But the landscape is slowly shifting towards a shiny new future with one major advancement being the fantastic Named Blocks RFC 226 by @machty. ☀️ ✨
The ultimate goal is to remove the need for the
columns
array and instead define the columns in the template. Maybe we'll also be able to remove the need forTable
objects.This issue is meant to serve as a brain dump and constant reminder. If you have ideas, wishes, questions or anything else related to this, please do add a comment! 😊
The text was updated successfully, but these errors were encountered: