javascript/ionic-framework
1
0
Fork 0
mirror of https://github.com/ionic-team/ionic-framework.git synced 2025-11-10 00:27:41 +08:00
Code Issues Packages Projects Releases Wiki Activity

docs(all): fix "aditional" typo (#15672)

Browse Source 
* docs(nav): fix typo

* docs: fix more `aditional` typings
This commit is contained in:
Daniel Sogl
2018-09-24 18:45:04 +02:00
committed by Manu MA
parent c2343ef55a
commit 7d50305b7f
5 changed files with 7 additions and 7 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
core/src/components.d.ts vendored
View File

@ -2825,7 +2825,7 @@ export namespace Components {
*/
'popToRoot': (opts?: NavOptions | null | undefined, done?: TransitionDoneFn | undefined) => Promise<boolean>;
/**
* 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': <T extends NavComponent>(component: T, componentProps?: ComponentProps<T> | null | undefined, opts?: NavOptions | null | undefined, done?: TransitionDoneFn | undefined) => Promise<boolean>;
/**
@ -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;
}

2
core/src/components/nav/nav.tsx
View File

@ -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<T extends NavComponent>(

2
core/src/components/nav/readme.md
View File

@ -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. |

2
core/src/components/router/readme.md
View File

@ -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

2
core/src/components/router/router.tsx
View File

@ -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.
*