Move default row count and pagination to the top of the table

[live-act]

Is your feature request related to a problem? Please describe.
Move the default row count and pagiantion to the the top of the table - similar to other more modern approach as shown in the flask-appbuilder example below

Describe the solution you'd like
For large tables (100K+ ), it makes more sense for users have a sense of how many records that they see and then apply filter to check what records need to be kept in viewing. The user experience is pretty bad when the row count and page number are down in the botton.

Describe alternatives you've considered
I have been using flask-appbuilder for building admin panels but I would like to try using starlette-admin in a new project.

[hasansezertasan]

A better approach would be adding an option to pick a location for the bar when defining an instance of Admin. Maybe in the future it would be configurable by the users, like dark/light theme which is like a good to have for a web page.

Edit: All that for nothing! I was playing with Starlette Admin Configuration, I found out a super cool stuff...

308 resolves your issue but you have to wait for 0.12.0.

Let me help you a bit more: How to display pagination on the top — DataTables forums

Datatables are awesome. I'm planning to create a pydantic model to validate datatables_options attribute. How is that sounds like @jowilf, do you think we need that?

[live-act]

Thank you @hasansezertasan ..! I will wait for 0.12.0 then. Appreciate your help.

[hasansezertasan]

You're welcome, can you close this issue?

[live-act]

Yes, of course. Thank you

[jowilf]

Thank you for your help @hasansezertasan.

I'm planning to create a pydantic model to validate datatables_options attribute. How is that sounds like @jowilf, do you think we need that?

I think it's necessary, we can't make pydantic a required dependency just to validate the datatables_options

[hasansezertasan]

Thank you for your help @hasansezertasan.

I'm planning to create a pydantic model to validate datatables_options attribute. How is that sounds like @jowilf, do you think we need that?

I think it's necessary, we can't make pydantic a required dependency just to validate the datatables_options

Oh, I'm confused. Should we have a validator for datatables_options or not?

[jowilf]

Oh, I'm confused. Should we have a validator for datatables_options or not?

Sorry i was saying it's not necessary

[hasansezertasan]

Thank you for your response.