-
Notifications
You must be signed in to change notification settings - Fork 173
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Extend instead of overwrite jpa repositories #113
Comments
Hi @cdalexndr ! I'm not sure I understand fully, isn't that already the case? See Lines 16 to 17 in 61ba124
I think the two configurations are only needed if you want that only some repositories receive the In any case, PR is welcome! |
Using this repository impl require overwriting the default repository factory bean to DataTablesRepositoryFactoryBean: Without this, the following repository:
results in error:
Using the Workaround is to group datatables repositories in packages and use
Instead of overwriting the base repository class, you should provide a repository fragment that when it's used by a repository will automatically decorate that repository and provide datatables functionality. See https://docs.spring.io/spring-data/jpa/docs/current/reference/html/#repositories.custom-implementations |
Instead of prodividing separate custom repositories for data table usage(DataTablesRepository), an extension mechanism would be better, like querydsl does (example QuerydslPredicateExecutor).
This also eases configuration, as there will not be required to provide two
@Configuration
instances.The text was updated successfully, but these errors were encountered: