As a developer, how many times in your life have you had to code endpoints to list flat data intended for a frontend in order to display a table with filters, sorting and pagination? 🤔
Even using the same technologies, all your projects will have a different implementation. By using hibernate you will use for example the criteria ? or maybe build your hql query based on dozens of criteria (filters and sorting)?
It is with the aim of overcoming this problem that the idea of smart-page was born. Smart-page will take care of the entire dynamic part of your requests in order to save you development time, reduce your code base and standardize your projects.
Using smart-page is very simple, you will only need to create a class representative of your table displayed in your frontend and add some annotations.
Spring implementations:
Smart-page does not manage your data source yet? Don't worry, smart-page has been designed to be as extensible as possible, both in terms of data source and also in terms of filters. You will find basic filters like equals, in, contains... but you can implement your own filters simply by registering them with the filter registration service.
many updates are planned like the management of mongodb, csv the addition of filter like "great than", "between" ..., but do not be afraid and open your pull request or simply submit your ideas
- manage multi executor in the classpath
- elasticsearch spring implementation
- sql / mongo / elasticsearch quarkus implementation
Smart-page is released under version 2.0 of the Apache License.