From 7d50305b7f6c48392dd278b55824e4c712890214 Mon Sep 17 00:00:00 2001 From: Daniel Sogl Date: Mon, 24 Sep 2018 18:45:04 +0200 Subject: [PATCH] docs(all): fix "aditional" typo (#15672) * docs(nav): fix typo * docs: fix more `aditional` typings --- core/src/components.d.ts | 6 +++--- core/src/components/nav/nav.tsx | 2 +- core/src/components/nav/readme.md | 2 +- core/src/components/router/readme.md | 2 +- core/src/components/router/router.tsx | 2 +- 5 files changed, 7 insertions(+), 7 deletions(-) diff --git a/core/src/components.d.ts b/core/src/components.d.ts index 04855bf564..5017c8f771 100644 --- a/core/src/components.d.ts +++ b/core/src/components.d.ts @@ -2825,7 +2825,7 @@ export namespace Components { */ 'popToRoot': (opts?: NavOptions | null | undefined, done?: TransitionDoneFn | undefined) => Promise; /** - * Push a new component onto the current navigation stack. Pass any aditional information along as an object. This additional information is accessible through NavParams + * Push a new component onto the current navigation stack. Pass any additional information along as an object. This additional information is accessible through NavParams */ 'push': (component: T, componentProps?: ComponentProps | null | undefined, opts?: NavOptions | null | undefined, done?: TransitionDoneFn | undefined) => Promise; /** @@ -3658,7 +3658,7 @@ export namespace Components { */ 'root': string; /** - * The router can work in two "modes": - With hash: `/index.html#/path/to/page` - Without hash: `/path/to/page` Using one or another might depend in the requirements of your app and/or where it's deployed. Usually "hash-less" navigation works better for SEO and it's more user friendly too, but it might requires aditional server-side configuration in order to properly work. On the otherside hash-navigation is much easier to deploy, it even works over the file protocol. By default, this property is `true`, change to `false` to allow hash-less URLs. + * The router can work in two "modes": - With hash: `/index.html#/path/to/page` - Without hash: `/path/to/page` Using one or another might depend in the requirements of your app and/or where it's deployed. Usually "hash-less" navigation works better for SEO and it's more user friendly too, but it might requires additional server-side configuration in order to properly work. On the otherside hash-navigation is much easier to deploy, it even works over the file protocol. By default, this property is `true`, change to `false` to allow hash-less URLs. */ 'useHash': boolean; } @@ -3676,7 +3676,7 @@ export namespace Components { */ 'root'?: string; /** - * The router can work in two "modes": - With hash: `/index.html#/path/to/page` - Without hash: `/path/to/page` Using one or another might depend in the requirements of your app and/or where it's deployed. Usually "hash-less" navigation works better for SEO and it's more user friendly too, but it might requires aditional server-side configuration in order to properly work. On the otherside hash-navigation is much easier to deploy, it even works over the file protocol. By default, this property is `true`, change to `false` to allow hash-less URLs. + * The router can work in two "modes": - With hash: `/index.html#/path/to/page` - Without hash: `/path/to/page` Using one or another might depend in the requirements of your app and/or where it's deployed. Usually "hash-less" navigation works better for SEO and it's more user friendly too, but it might requires additional server-side configuration in order to properly work. On the otherside hash-navigation is much easier to deploy, it even works over the file protocol. By default, this property is `true`, change to `false` to allow hash-less URLs. */ 'useHash'?: boolean; } diff --git a/core/src/components/nav/nav.tsx b/core/src/components/nav/nav.tsx index d7f6bcdced..b1a2e3c5d5 100644 --- a/core/src/components/nav/nav.tsx +++ b/core/src/components/nav/nav.tsx @@ -142,7 +142,7 @@ export class Nav implements NavOutlet { } /** - * Push a new component onto the current navigation stack. Pass any aditional information along as an object. This additional information is accessible through NavParams + * Push a new component onto the current navigation stack. Pass any additional information along as an object. This additional information is accessible through NavParams */ @Method() push( diff --git a/core/src/components/nav/readme.md b/core/src/components/nav/readme.md index accb368898..c0963dd37f 100644 --- a/core/src/components/nav/readme.md +++ b/core/src/components/nav/readme.md @@ -41,7 +41,7 @@ Unlike RouterOutlet, Nav is not tied to a particular router. Meaning that if we | `pop` | Call to navigate back from a current component. Similar to push(), you can also pass navigation options. | | `popTo` | Pop to a specific index in the navigation stack | | `popToRoot` | Navigate back to the root of the stack, no matter how far back that is. | -| `push` | Push a new component onto the current navigation stack. Pass any aditional information along as an object. This additional information is accessible through NavParams | +| `push` | Push a new component onto the current navigation stack. Pass any additional information along as an object. This additional information is accessible through NavParams | | `removeIndex` | Removes a page from the nav stack at the specified index. | | `setPages` | Set the views of the current navigation stack and navigate to the last view. By default animations are disabled, but they can be enabled by passing options to the navigation controller.You can also pass any navigation params to the individual pages in the array. | | `setRoot` | Set the root for the current navigation stack. | diff --git a/core/src/components/router/readme.md b/core/src/components/router/readme.md index 08f975f8f5..ec00f518fb 100644 --- a/core/src/components/router/readme.md +++ b/core/src/components/router/readme.md @@ -23,7 +23,7 @@ If you're using Angular, please see [ion-router-outlet](../router-outlet) instea | Property | Attribute | Description | Type | | --------- | ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------- | | `root` | `root` | By default `ion-router` will match the routes at the root path ("/"). That can be changed when | `string` | -| `useHash` | `use-hash` | The router can work in two "modes": - With hash: `/index.html#/path/to/page` - Without hash: `/path/to/page` Using one or another might depend in the requirements of your app and/or where it's deployed. Usually "hash-less" navigation works better for SEO and it's more user friendly too, but it might requires aditional server-side configuration in order to properly work. On the otherside hash-navigation is much easier to deploy, it even works over the file protocol. By default, this property is `true`, change to `false` to allow hash-less URLs. | `boolean` | +| `useHash` | `use-hash` | The router can work in two "modes": - With hash: `/index.html#/path/to/page` - Without hash: `/path/to/page` Using one or another might depend in the requirements of your app and/or where it's deployed. Usually "hash-less" navigation works better for SEO and it's more user friendly too, but it might requires additional server-side configuration in order to properly work. On the otherside hash-navigation is much easier to deploy, it even works over the file protocol. By default, this property is `true`, change to `false` to allow hash-less URLs. | `boolean` | ## Events diff --git a/core/src/components/router/router.tsx b/core/src/components/router/router.tsx index 196672a4f6..d8bf2724b9 100644 --- a/core/src/components/router/router.tsx +++ b/core/src/components/router/router.tsx @@ -42,7 +42,7 @@ export class Router implements ComponentInterface { * Using one or another might depend in the requirements of your app and/or where it's deployed. * * Usually "hash-less" navigation works better for SEO and it's more user friendly too, but it might - * requires aditional server-side configuration in order to properly work. + * requires additional server-side configuration in order to properly work. * * On the otherside hash-navigation is much easier to deploy, it even works over the file protocol. *