hendrik/lens
1
0 Fork 0
mirror of https://github.com/lensapp/lens.git synced 2025-05-20 05:10:56 +00:00
Code Issues Projects Releases Wiki Activity

fix typos found in review

Browse Source 
Signed-off-by: Jim Ehrismann <jehrismann@mirantis.com>
This commit is contained in:
Jim Ehrismann committed 2020-12-03 14:16:13 -05:00
1 parent 95d11c3fcd
commit ce97ff2f28
1 file changed
+4 -4
Download Patch File Download Diff File Expand all files Collapse all files
docs/extensions/guides/renderer-extension.md
+4 -4
View File
@@ -57,10 +57,10 @@ export default class ExampleExtension extends LensRendererExtension {
```
Cluster pages are objects matching the `PageRegistration` interface.
The `id` field identiifies the page, and at its simplest is just a string identifier, as shown in the example above.
The `id` field identifies the page, and at its simplest is just a string identifier, as shown in the example above.
The 'id' field can also convey route path details, such as variable parameters provided to a page ([See example below]()).
The `components` field matches the `PageComponents` interface for wich there is one field, `Page`.
`Page` is of type ` React.ComponentType<any>`, which gives you great flexibility in defining the appearance and behaviour of your page.
`Page` is of type ` React.ComponentType<any>`, which gives you great flexibility in defining the appearance and behaviour of your page.
For the example above `ExamplePage` can be defined in `page.tsx`:
``` typescript
@@ -239,10 +239,10 @@ export default class HelpExtension extends LensRendererExtension {
```
Global pages are objects matching the `PageRegistration` interface.
The `id` field identiifies the page, and at its simplest is just a string identifier, as shown in the example above.
The `id` field identifies the page, and at its simplest is just a string identifier, as shown in the example above.
The 'id' field can also convey route path details, such as variable parameters provided to a page ([See example below]()).
The `components` field matches the `PageComponents` interface for which there is one field, `Page`.
`Page` is of type ` React.ComponentType<any>`, which gives you great flexibility in defining the appearance and behaviour of your page.
`Page` is of type ` React.ComponentType<any>`, which gives you great flexibility in defining the appearance and behaviour of your page.
For the example above `HelpPage` can be defined in `page.tsx`:
``` typescript