Resources:
Before submitting an issue, please consult our docs.
Stencil version: (run npm list @stencil/core from a terminal/cmd prompt and paste output below):
+-- @stencil/core@2.19.3
+-- @stencil/sass@2.0.0
| `-- @stencil/core@2.19.3 deduped
`-- stencil-router-v2@0.6.0
+-- @stencil/core@2.19.3 deduped
`-- @stencil/store@1.5.0
`-- @stencil/core@2.19.3 deduped
I'm submitting a ... (check one with "x")
[ ] bug report
[x] feature request
[ ] support request => Please do not submit support requests here, use one of these channels: https://forum.ionicframework.com/ or https://stencil-worldwide.slack.com
Current behavior:
There is currently 1 supported way to programmatically navigate to another route: Router.push(url: string).
Expected behavior:
history.pushState accepts a state object as the first argument. It would be very helpful if Router.push() accepted a second (optional) argument for that purpose.
Furthermore, it would be great if the library supported not only pushState, but also history.replaceState, e.g. Router.replace(). This is currently a blocker for us to move to this library.
Resources:
Before submitting an issue, please consult our docs.
Stencil version: (run
npm list @stencil/corefrom a terminal/cmd prompt and paste output below):I'm submitting a ... (check one with "x")
[ ] bug report
[x] feature request
[ ] support request => Please do not submit support requests here, use one of these channels: https://forum.ionicframework.com/ or https://stencil-worldwide.slack.com
Current behavior:
There is currently 1 supported way to programmatically navigate to another route:
Router.push(url: string).Expected behavior:
history.pushStateaccepts a state object as the first argument. It would be very helpful ifRouter.push()accepted a second (optional) argument for that purpose.Furthermore, it would be great if the library supported not only pushState, but also
history.replaceState, e.g.Router.replace(). This is currently a blocker for us to move to this library.