third_codes/mapstruct
1
0
Fork 0
mirror of https://github.com/mapstruct/mapstruct.git synced 2025-07-12 00:00:08 +08:00
Code Issues Packages Projects Releases Wiki Activity

Update Typos in javadoc (#2958)

Browse Source
This commit is contained in:
Prasanth Omanakuttan 2022-08-20 17:07:43 +05:30 committed by Filip Hrisafov
parent 62e73464b2
commit e3f9a1ccd5
4 changed files with 7 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
core/src/main/java/org/mapstruct/InheritInverseConfiguration.java
View File

@ -81,8 +81,8 @@ import java.lang.annotation.Target;
public @interface InheritInverseConfiguration { public @interface InheritInverseConfiguration {
/** /**
* The name of the inverse mapping method to inherit the mappings from. Needs only to be specified in case more than * The name of the inverse mapping method to inherit the mappings from. Needs to be specified only in case more than
* one inverse method with matching source and target type exists. * one inverse method exists with a matching source and target type exists.
* *
* @return The name of the inverse mapping method to inherit the mappings from. * @return The name of the inverse mapping method to inherit the mappings from.
*/ */

2
processor/src/main/java/org/mapstruct/ap/spi/AstModifyingAnnotationProcessor.java
View File

@ -15,7 +15,7 @@ import org.mapstruct.util.Experimental;
* <p> * <p>
* This contract will be queried by MapStruct when examining types referenced by mappers to be generated, most notably * This contract will be queried by MapStruct when examining types referenced by mappers to be generated, most notably
* the source and target types of mapping methods. If at least one AST-modifying processor announces further changes to * the source and target types of mapping methods. If at least one AST-modifying processor announces further changes to
* such type, the generation of the affected mapper(s) will be deferred to a future round in the annnotation processing * such type, the generation of the affected mapper(s) will be deferred to a future round in the annotation processing
* cycle. * cycle.
* <p> * <p>
* Implementations are discovered via the service loader, i.e. a JAR providing an AST-modifying processor needs to * Implementations are discovered via the service loader, i.e. a JAR providing an AST-modifying processor needs to

4
processor/src/main/java/org/mapstruct/ap/spi/FreeBuilderAccessorNamingStrategy.java
View File

@ -20,8 +20,8 @@ import org.mapstruct.util.Experimental;
* <li>{@code mergeFrom(Target.Builder)}</li> * <li>{@code mergeFrom(Target.Builder)}</li>
* </ul> * </ul>
* <p> * <p>
* When the JavaBean convention is not used with FreeBuilder then the getters are non standard and MapStruct * When the JavaBean convention is not used with FreeBuilder then the getters are non-standard and MapStruct
* won't recognize them. Therefore one needs to use the JavaBean convention in which the fluent setters * won't recognize them. Therefore, one needs to use the JavaBean convention in which the fluent setters
* start with {@code set}. * start with {@code set}.
* *
* @author Filip Hrisafov * @author Filip Hrisafov

4
processor/src/main/java/org/mapstruct/ap/spi/ImmutablesAccessorNamingStrategy.java
View File

@ -10,9 +10,9 @@ import javax.lang.model.element.ExecutableElement;
import org.mapstruct.util.Experimental; import org.mapstruct.util.Experimental;
/** /**
* Accesor naming strategy for Immutables. * Accessor naming strategy for Immutables.
* The generated Immutables also have a from that works as a copy. Our default strategy considers this method * The generated Immutables also have a from that works as a copy. Our default strategy considers this method
* as a setter with a name {@code from}. Therefore we are ignoring it. * as a setter with a name {@code from}. Therefore, we are ignoring it.
* *
* @author Filip Hrisafov * @author Filip Hrisafov
*/ */