Is there an existing issue for this?
Is your feature request related to a problem? Please describe the problem.
The table component now is awesome and complicated. Usually, when allowing user to customize the functions by template, it might need more features for cusomization. Here is what I can see while using the Table component.
- The Table component allows user to add/edititems by setting properties. However, there is no AddTemplate. sometimes, the content of Addint an item is not the same as Editing an item. So it's better to have AddTemplate, whne the AddTemplate doesn't exists, then use EditTemplate.
- When using SearchModel, the filtering model type might be different to the table item type, so there should have another optional TFilter type, say Employee is the row item type with properties: (FirstName, LastName, DateOfBirth, Nationality [Countries] etc), the filter type might be: (NameSearchText, Age [ could be: Senior, Adult, Child, Baby ], Nationality [could be: China, New Zealand, Others]). hope we could allow user to customize the filtering model.
- the EditMode are good, could we have another option "Drawer"? so we can show the add/edit form at the right drawer. this is a popular option now.
This might be a bit too much. As some scenario might not need such features, in my option. the Table component can be split into two components, one is just for showing filtering/searching/sorting and results. The other one can have filtering/searching/sorting/add/edit/delete operations.
Thank you for all the hard work. I love this library.
Describe the solution you'd like
Some thoughts of possible solutions:
- split the Table component to Table, AdvanceTable (or DataManageTable?), the Table component is just for filtering/searching/sorting
- having optional AddTemplate in place
- adding support for separating Filter model type.
- adding support for showing add/edit form as drawer (usually right side)
Additional context
No response
Is there an existing issue for this?
Is your feature request related to a problem? Please describe the problem.
The table component now is awesome and complicated. Usually, when allowing user to customize the functions by template, it might need more features for cusomization. Here is what I can see while using the Table component.
This might be a bit too much. As some scenario might not need such features, in my option. the Table component can be split into two components, one is just for showing filtering/searching/sorting and results. The other one can have filtering/searching/sorting/add/edit/delete operations.
Thank you for all the hard work. I love this library.
Describe the solution you'd like
Some thoughts of possible solutions:
Additional context
No response