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

Fix typos in documentations.

Browse Source 
Fix typos in READMEs, javadoc, comments and code.

Original pull request #642
This commit is contained in:
Marc Wrobel
2022-07-18 16:43:44 +02:00
committed by Jens Schauder
parent 1aec184ff0
commit ce994f9ea0
57 changed files with 83 additions and 83 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
web/example/src/main/java/example/users/Password.java
View File

@@ -56,7 +56,7 @@ public class Password implements CharSequence {
/**
* Creates a new encrypted {@link Password} for the given {@link String}. Note how this method is package protected so
* that encrypted passwords can only created by components in this package and not accidentally by clients using the
* that encrypted passwords can only be created by components in this package and not accidentally by clients using the
* type from other packages.
*
* @param password must not be {@literal null} or empty.

2
web/example/src/main/java/example/users/web/UserController.java
View File

@@ -58,7 +58,7 @@ class UserController {
private final UserManagement userManagement;
/**
* Equis the model with a {@link Page} of {@link User}s. Spring Data automatically populates the {@link Pageable} from
* Populates the model with a {@link Page} of {@link User}s. Spring Data automatically populates the {@link Pageable} from
* request data according to the setup of {@link PageableHandlerMethodArgumentResolver}. Note how the defaults can be
* tweaked by using {@link PageableDefault}.
*

4
web/projection/README.md
View File

@@ -22,9 +22,9 @@ This type is used in `UserController.index(…)` and basically combines two mode
## Binding request data via JSON Path expression
The `@JsonPath` annotations bind the values obtained by evaluating the expressions from the request. The sample is using a recursive property lookup for `firstname` and `lastname`. Using those expressions allows the payload thats received to slightly changed and the code dealing with not having to be changed.
The `@JsonPath` annotations bind the values obtained by evaluating the expressions from the request. The sample is using a recursive property lookup for `firstname` and `lastname`. Using those expressions allows the payload that received to slightly changed and the code dealing with not having to be changed.
As an example using that on the server side can be found in `UserControllerIntegrationTests`. The tests sends two different flavors of JSON to simulate a change in behavior of the client and the server can handle both representation formats without the need for a change.
As an example using that on the server side can be found in `UserControllerIntegrationTests`. The tests send two different flavors of JSON to simulate a change in behavior of the client and the server can handle both representation formats without the need for a change.
This is also very useful on the client side which is simulated in `UserControllerClientTests` setting up a `RestTemplate` with the newly introduced `HttpMessageConverters` so that the projection interface can be used to access the payload. See how the test case accesses different HTTP resources, that simulate a change in the representation on the server side.

4
web/querydsl/README.md
View File

@@ -30,7 +30,7 @@ class UserController {
}
```
As you can see `Predicate` can be used as Spring MVC controller argument. It will automatically populate such a `Predicate` with values from the current request based on the type configured in `@QuerydslPredicate`. Explicit bindings can be configured by either explictly defining one in the annotation, too. By default, we will inspect the domain types's repository for binding customizations. In this example, it looks like this:
As you can see `Predicate` can be used as Spring MVC controller argument. It will automatically populate such a `Predicate` with values from the current request based on the type configured in `@QuerydslPredicate`. Explicit bindings can be configured by either explicitly defining one in the annotation, too. By default, we will inspect the domain types's repository for binding customizations. In this example, it looks like this:
```java
public interface UserRepository
@@ -45,7 +45,7 @@ public interface UserRepository
}
```
The repository extends `QuerydslBinderCustomizer` which exposes a `QuerydslBindings` instance for customization. It allows for property based (by using Querydsl's meta-model types) and type based customizations of the value binding. The example here defines a `String`-properties to be bound using the `containsIgnoreCase(…)` operator. For further information checkout the JavaDoc of [QuerydslBindings](http://docs.spring.io/spring-data/commons/docs/1.11.0.RC1/api/org/springframework/data/querydsl/binding/QuerydslBindings.html).
The repository extends `QuerydslBinderCustomizer` which exposes a `QuerydslBindings` instance for customization. It allows for property based (by using Querydsl's metamodel types) and type based customizations of the value binding. The example here defines a `String`-properties to be bound using the `containsIgnoreCase(…)` operator. For further information checkout the JavaDoc of [QuerydslBindings](http://docs.spring.io/spring-data/commons/docs/1.11.0.RC1/api/org/springframework/data/querydsl/binding/QuerydslBindings.html).
## Technologies used

4
web/querydsl/src/main/resources/templates/index.html
View File

@@ -79,7 +79,7 @@
</td>
<td th:text="${user.firstname}">Firstname</td>
<td th:text="${user.lastname}">Lastname</td>
<td th:text="${user.nationality}">Naionality</td>
<td th:text="${user.nationality}">Nationality</td>
<td th:text="${user.address.city}">City</td>
<td th:text="${user.address.street}">Street</td>
<td th:text="${user.email}">Email</td>
@@ -92,4 +92,4 @@
</div>
</body>
</html>
</html>