You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: user-manual/providers.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -36,7 +36,7 @@ Providers can be configured for use in different contexts:
36
36
37
37
### By ModelMapper
38
38
39
-
A provider can be configured for a `ModelMapper` instance to provide instances of _all_ destination types during the mapping process. This is particularly useful for delegating object provisioning to an IoC container (See the [Spring](/user-manual/extensions#spring) and [Guice](/user-manual/extensions#guice) extensions for more on this).
39
+
A provider can be configured for a `ModelMapper` instance to provide instances of _all_ destination types during the mapping process. This is particularly useful for delegating object provisioning to an IoC container (See the [Spring](/user-manual/spring-integration) and [Guice](/user-manual/guice-integration) integrations for more on this).
@@ -62,4 +62,4 @@ Finally, providers can be used to provide instances of specific properties. See
62
62
63
63
### Notes
64
64
65
-
If you don't want to or can't construct a requested type, you can always return `null` from a Provider and ModelMapper will construct the type for you.
65
+
If you don't want to or can't construct a requested type, you can always return `null` from a Provider and ModelMapper will construct the type for you.
0 commit comments