You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If you have selected a module in the tree and refresh the whole page, the loaded page won't be at the selected module but back to the root. The same happens if you select a processing by date.
One way to fix this would be to make the module id and processing id part of the route.
The text was updated successfully, but these errors were encountered:
When refreshing the page, adding the module id and the processing id on the route should solve the problem.
But when selecting a processing by date the situation is more subtle because the module may not exist on different times of the same project. Also, the processing id is different and we cannot guarantee that the module will have the same id.
We could search for the module name, but even then the module may not exist on the selected date.
For that case, I think the best approach is to simply go back to the root.
If you have selected a module in the tree and refresh the whole page, the loaded page won't be at the selected module but back to the root. The same happens if you select a processing by date.
One way to fix this would be to make the module id and processing id part of the route.
The text was updated successfully, but these errors were encountered: