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.

Sign up for GitHub

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

Jump to bottom

router cache stores wrong state #45

Closed
thomashandorf opened this issue Nov 21, 2016 · 1 comment
Closed

router cache stores wrong state #45

thomashandorf opened this issue Nov 21, 2016 · 1 comment
Assignees
@kennytordeur
Labels
bug prio:normal

Comments

@thomashandorf
Copy link
Member

when having the cache active and changing the state outside the router (gesture or api) the current caching mechanism will store the state only during the next routing event. So this will actually store the state after the gesture and api changes but not the state that was initally set during the former routing event

We need a way to store in the cache once the new state is set after an routing event
thomashandorf added a commit that referenced this issue Nov 21, 2016
@thomashandorf
layerjs.js: disable cache completely until we find a solution for wro…
d3f4c93 
…ngly stored stages (see issue #45)
@thomashandorf
Copy link
Member Author

we disabled the cache. That should fix it.We added a separate cache only for the filerouter.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@kennytordeur kennytordeur

Labels
bug prio:normal
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@thomashandorf @kennytordeur