Replies: 1 comment
-
FiltersCurrent plan for filters is the following:
|
Beta Was this translation helpful? Give feedback.
-
FiltersCurrent plan for filters is the following:
|
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Roadmap
This is very high level, and isn't complete by any means, as I've been pretty focused on getting V3 into a beta state.
However, this does highlight what I'm conscious of in terms of feature improvements for v3.x onwards. A good chunk of the below is complete and I just need to write documentation/tests.
Note that this doesn't cover general improvements (such as implementing locked properties, adding missing return types/type-hints) improving the test suite, and looking at general performance improvements.
If there's a feature request that I've obviously overlooked, then please do suggest it on Discord, or add a comment here.
Filters
The following is what I intend to do for v3.x post-release.
New Filters
Improvements
Filter Validation
Each filter type has its own validation methodology to ensure that data entered is what it should be, plan currently is to:
Columns
I don't have an awful lot planned here, introduction of a couple of new Column types, and some improvements to collapse behaviour.
New Columns
Improvements
Miscellaneous
Styling
I've seen that there's some demand for setting custom classes on some of the inputs, and it's planned to allow for customisation of these in the same way that the rest of the table is customisable.
Features
Beta Was this translation helpful? Give feedback.
All reactions