Is your feature request related to a problem? Please describe.
In most of the projects I have been involved with, having custom and searchable table views was the primary request. An example project is LatteDB and in particular the progress views which utilize the Django REST framework. Having such an API as a default is desirable for EspressoDB.
Describe the solution you'd like
If possible, I'd like to keep the dependency tree small. Thus I would prefer to only have the rest framework with datatables as a dependency in EspressoDB if a user explicitly requests it. Still, having the same API as in LatteDB might be beneficial for future implementations. E.g., copy the view implementation from the FileStatusView in LatteDB and implement the views with a js datatables CDN. An extension to REST will be explained in the docs.
Is your feature request related to a problem? Please describe.
In most of the projects I have been involved with, having custom and searchable table views was the primary request. An example project is LatteDB and in particular the progress views which utilize the Django REST framework. Having such an API as a default is desirable for EspressoDB.
Describe the solution you'd like
If possible, I'd like to keep the dependency tree small. Thus I would prefer to only have the rest framework with datatables as a dependency in EspressoDB if a user explicitly requests it. Still, having the same API as in LatteDB might be beneficial for future implementations. E.g., copy the view implementation from the FileStatusView in LatteDB and implement the views with a js datatables CDN. An extension to REST will be explained in the docs.