@stacknav/angular 0.1.2 → 0.1.3
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +7 -0
- package/package.json +2 -2
package/README.md
CHANGED
|
@@ -127,6 +127,13 @@ provideStackNav({
|
|
|
127
127
|
A strategy receives `{ from, to, trigger, historyDelta, hint, stack }`, where
|
|
128
128
|
`from` and `to` carry `{ key, segments, level, data, snapshot }`.
|
|
129
129
|
|
|
130
|
+
Because `data` is the route's own data, a strategy can work off metadata your
|
|
131
|
+
routes already carry. An app that names its routes the way Angular's
|
|
132
|
+
route-transition recipe does (`data: { animation: 'Thread' }`) keeps those names
|
|
133
|
+
and adds one strategy that looks the from/to pair up in a
|
|
134
|
+
`transition('Inbox => Thread')`-style table; see the Mail demo's
|
|
135
|
+
[`animation.ts`](../../apps/angular-demo/src/app/demos/mail/animation.ts).
|
|
136
|
+
|
|
130
137
|
### Back buttons
|
|
131
138
|
|
|
132
139
|
A back button is `Location.back()`. After a deep link there is nothing to go back
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@stacknav/angular",
|
|
3
|
-
"version": "0.1.
|
|
3
|
+
"version": "0.1.3",
|
|
4
4
|
"description": "Angular router outlet with iOS-style push/pop transitions and interactive swipe back, built on @stacknav/core.",
|
|
5
5
|
"license": "MIT",
|
|
6
6
|
"keywords": [
|
|
@@ -21,7 +21,7 @@
|
|
|
21
21
|
},
|
|
22
22
|
"dependencies": {
|
|
23
23
|
"tslib": "^2.8.0",
|
|
24
|
-
"@stacknav/core": "^0.3.
|
|
24
|
+
"@stacknav/core": "^0.3.1"
|
|
25
25
|
},
|
|
26
26
|
"sideEffects": false,
|
|
27
27
|
"type": "module",
|