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
Integration with a grpc generated rest gateway, which stored fetched data in ngrx/store, using the url as the first source of truth for the sorting, pagination, and filtering.
Support for edit, delete and view detail links in the table rows.
The user would then only have to pass a few configuration parameters to the generator and have a fully functioning datatable. They could then modify the behavior via editing the json passed as an @Input() property to the Simple Table abstraction, and edit the styling to fit their application. This could make such data tables take a day to build instead of a few weeks.
Future versions could broaden the applicability of such a component in various ways:
Server idl support:
graphql schema
raml
json schema
api blueprint.
Simplified custom behavior:
Opt out of ngrx/store
Opt out of sorting, filtering, pagination stored in the url.
Allow passing custom components for table headers, table columns, pagination.
Simplified custom styling:
Well documented ways to override material's default styles as needed
More related generators to address forms to edit items in each row.
The text was updated successfully, but these errors were encountered:
Not everyone wants to use material or the material table. Therefore this should not be implemented in the default schematics (new blueprint engine). Documentation is coming soon with information about how to create your own custom schematics.
Closing this issue because it will not be implemented by the CLI.
Bug Report or Feature Request (mark with an
x
)Desired functionality.
A generator for a material table using a schema from a common idl.
The standard way of creating a table with sorting, filtering, and pagination from a well known schema is unnecessarily time consuming.
Mention any other details that might be useful.
There are a lot of details in this. The issue is meant to invite discussion.
A great start would be:
The user would then only have to pass a few configuration parameters to the generator and have a fully functioning datatable. They could then modify the behavior via editing the json passed as an
@Input()
property to the Simple Table abstraction, and edit the styling to fit their application. This could make such data tables take a day to build instead of a few weeks.Future versions could broaden the applicability of such a component in various ways:
The text was updated successfully, but these errors were encountered: