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

Any ETA for navigation reference? #33

Open
prasshantg opened this issue May 6, 2020 · 4 comments
Open

Any ETA for navigation reference? #33

prasshantg opened this issue May 6, 2020 · 4 comments

Comments

@prasshantg
Copy link

I am looking for reference to develop wizard using micro-frontends. I suppose the navigation reference should cover it. Do you have any ETA for it? Or any documentation how to achieve it?

@16pxdesign
Copy link

I would also be interested in continuing the topic

@dkowis
Copy link

dkowis commented Mar 1, 2023

Two years later...

@teone
Copy link

teone commented Apr 1, 2023

+1 interested in the topic as well

@brent8642
Copy link

I've done navigations by changing the window.location within a custom event handler to load the page of the new location.

Event handler:
window.location.href = "https://mysite.com?my_arg=fun-times"

Otherwise, you're behaving like a single page app and changing the DOM per custom event handling or an async POST/GET to the server, but not loading a page entirely. Perhaps even modifying the URL like you see when clicking an anchor link that jumps to a location but doesn't load from the server.

The concept is similar to other things mentioned in the artile:

  1. Use the DOM API to load a new page within a custom event handler
  2. Or use SPA behavior, modifying the DOM to make an illusion of a new page
  3. Modify URL if necessary (and implement custom events for navigating backwards or forwards)

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

5 participants