Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Navigation: Improve .push() and introduce .replace() method #148

Open
bugii opened this issue Jan 20, 2023 · 0 comments
Open

Navigation: Improve .push() and introduce .replace() method #148

bugii opened this issue Jan 20, 2023 · 0 comments

Comments

@bugii
Copy link

bugii commented Jan 20, 2023

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/[email protected]                                        
+-- @stencil/[email protected]                                         
| `-- @stencil/[email protected] deduped                              
`-- [email protected]                                     
  +-- @stencil/[email protected] deduped                              
  `-- @stencil/[email protected]                                      
    `-- @stencil/[email protected] 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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant