Fix typos in documentations.
Fix typos in READMEs, javadoc, comments and code. Original pull request #642
This commit is contained in:
committed by
Jens Schauder
parent
1aec184ff0
commit
ce994f9ea0
@@ -15,7 +15,7 @@
|
||||
|
||||
<name>Spring Data JDBC - How to model bidirectional relationships between aggregates</name>
|
||||
<description>Sample project for Spring Data JDBC demonstrating how to model bidirectional relationships between aggregates.
|
||||
It serves as a source code repository for a How To article on the Spring Blog</description>
|
||||
It serves as a source code repository for a How-To article on the Spring Blog</description>
|
||||
<url>https://projects.spring.io/spring-data-jdbc</url>
|
||||
<inceptionYear>2021</inceptionYear>
|
||||
</project>
|
||||
</project>
|
||||
|
||||
@@ -15,7 +15,7 @@
|
||||
|
||||
<name>Spring Data JDBC - How to model aggregate internal bidirectional relationships</name>
|
||||
<description>Sample project for Spring Data JDBC demonstrating how to model aggregate internal bidirectional relationships.
|
||||
It serves as a source code repository for a How To article on the Spring Blog</description>
|
||||
It serves as a source code repository for a How-To article on the Spring Blog</description>
|
||||
<url>https://projects.spring.io/spring-data-jdbc</url>
|
||||
<inceptionYear>2021</inceptionYear>
|
||||
</project>
|
||||
</project>
|
||||
|
||||
@@ -13,7 +13,7 @@
|
||||
|
||||
<name>Spring Data JDBC - How to ID generation</name>
|
||||
<description>Sample project for Spring Data JDBC demonstrating the various options to use user defined IDs in Spring Data JDBC aggregates.
|
||||
It serves as a source code repository for a How To article on the Spring Blog</description>
|
||||
It serves as a source code repository for a How-To article on the Spring Blog</description>
|
||||
<url>https://projects.spring.io/spring-data-jdbc</url>
|
||||
<inceptionYear>2021</inceptionYear>
|
||||
|
||||
|
||||
@@ -84,7 +84,7 @@ class Application {
|
||||
@Override
|
||||
public <T> T mapRow(RelationalPersistentEntity<T> entity, ResultSet resultSet, Object key) {
|
||||
|
||||
// rows will not mapped to the entity interface, but to its implementation generated by Immutable
|
||||
// rows will not be mapped to the entity interface, but to its implementation generated by Immutable
|
||||
RelationalPersistentEntity<T> implementationEntity = getImplementationEntity(mappingContext, entity);
|
||||
return super.mapRow(implementationEntity, resultSet, key);
|
||||
}
|
||||
@@ -93,7 +93,7 @@ class Application {
|
||||
public <T> T mapRow(PersistentPropertyPathExtension path, ResultSet resultSet, Identifier identifier,
|
||||
Object key) {
|
||||
|
||||
// rows will not mapped to the entity interface, but to its implementation generated by Immutable
|
||||
// rows will not be mapped to the entity interface, but to its implementation generated by Immutable
|
||||
RelationalPersistentEntity<?> implementationEntity = getImplementationEntity(mappingContext,
|
||||
path.getLeafEntity());
|
||||
var propertyPath = new DelegatePersistentPropertyPathExtension(mappingContext,
|
||||
|
||||
@@ -7,4 +7,4 @@ The map of models is maintained by two statements configured in MyBatis mappings
|
||||
|
||||
`example.springdata.jdbc.mybatis.LegoSetMapper.findAllByProperty-models` showcases how a map can be loaded by configuring the select to return instances of `Map.Entry`
|
||||
|
||||
`example.springdata.jdbc.mybatis.Model.insert` showcases how one can access the `MyBatixContext` and thereby the instance to save and the key of the parent entity.
|
||||
`example.springdata.jdbc.mybatis.Model.insert` showcases how one can access the `MyBatisContext` and thereby the instance to save and the key of the parent entity.
|
||||
|
||||
Reference in New Issue
Block a user