Spring/spring-data-commons
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Polishing.

Browse Source 
Fix Querydsl lettercasing.

See #3243
This commit is contained in:
Mark Paluch
2025-02-13 09:13:48 +01:00
parent 232a3da2c8
commit 15f254b75e
2 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
src/main/antora/modules/ROOT/pages/repositories/core-extensions-web.adoc
View File

@@ -348,7 +348,7 @@ For more information, see the https://github.com/spring-projects/spring-data-exa
[[core.web.type-safe]]
== Querydsl Web Support
For those stores that have http://www.querydsl.com/[QueryDSL] integration, you can derive queries from the attributes contained in a `Request` query string.
For those stores that have http://www.querydsl.com/[Querydsl] integration, you can derive queries from the attributes contained in a `Request` query string.
Consider the following query string:

2
src/main/antora/modules/ROOT/pages/repositories/custom-implementations.adoc
View File

@@ -67,7 +67,7 @@ interface UserRepository extends CrudRepository<User, Long>, CustomizedUserRepos
Extending the fragment interface with your repository interface combines the CRUD and custom functionality and makes it available to clients.
Spring Data repositories are implemented by using fragments that form a repository composition.
Fragments are the base repository, functional aspects (such as xref:repositories/core-extensions.adoc#core.extensions.querydsl[QueryDsl]), and custom interfaces along with their implementations.
Fragments are the base repository, functional aspects (such as xref:repositories/core-extensions.adoc#core.extensions.querydsl[Querydsl]), and custom interfaces along with their implementations.
Each time you add an interface to your repository interface, you enhance the composition by adding a fragment.
The base repository and repository aspect implementations are provided by each Spring Data module.