Skip to content

Commit 2f57799

Browse files
committed
Fix links in field provider page
1 parent b9a5732 commit 2f57799

File tree

1 file changed

+4
-3
lines changed

1 file changed

+4
-3
lines changed

packages/react-renderer-demo/src/app/pages/renderer/field-provider.md

Lines changed: 4 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,5 @@
1-
import Link from 'next/link';
1+
import RouterNav from 'next/link';
2+
import Link from '@material-ui/core/Link';
23

34
### Field Provider
45
import Grid from '@material-ui/core/Grid'
@@ -22,11 +23,11 @@ which adds additional methods that will help you to control your form state.
2223
### Accessing FieldProvider
2324

2425
To use Fieldprovider, you first need to register a component to your component mapper.
25-
You can read more about that in <Link href="/renderer/component-mapping"><a>Component mapping</a></Link>.
26+
You can read more about that in <RouterNav href="/renderer/component-mapping"><Link>Component mapping</Link></RouterNav>.
2627

2728
Each component will receive FieldProvider as a prop. Be aware that pre-defined component types are
2829
automatically wrapped in FieldProvider. This is done to make it easier to create component mappers for
29-
standard form components. List of standard components is available <Link href="/renderer/component-api"><a>here</a></Link>.
30+
standard form components. List of standard components is available <RouterNav href="/renderer/component-api"><Link>here</Link></RouterNav>.
3031

3132
### Using FieldProvider
3233

0 commit comments

Comments
 (0)