Reflecting UI changes to the route
See original GitHub issueSometimes this would be grate to have UI state in route. for example in a list that is filtered with some check boxes. When the user clicks on a checkbox I like the route to change so that the user is able to share that route or bookmark it. I don’t want to use #
since Google will ignore it. currently if I do something like this:
import history from './history';
history.replace('/itemts/filter=discount,new');
It will change the position of my scroll. How can I implement such a thing?
Issue Analytics
- State:
- Created 6 years ago
- Comments:8 (4 by maintainers)
Top Results From Across the Web
Reflect changes of same Vue Component to different routes
1 Answer 1 · Global Event Bus - keep the active tab in a global EventBus state that will also listen to changes,...
Read more >Overview of UI-Router React and comparison with React Router
It's a drop-in utility that lets you visualize the state tree and transitions of your UI-Router application. It's written in React, and works...
Read more >Using UI-Router for better React routing | by Scott Carmichael
To trigger a transition; state names are used, not urls. The easiest way to change state is using the UISref component, which is...
Read more >push a new route only triggers URL change but not location ...
set up the connected-react-router as doc. but it only update the url rather than the location object when yield put(push( /somewhere )) in ......
Read more >Change And Its Detection In JavaScript Frameworks
This can happen when the user interacts with the UI, or when something else happens in the world that updates the data. The...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
You need to decide in which case you don’t need to scroll. For example you may skip scrolling if path wasn’t changed or if
history.replace
were used.