-
Notifications
You must be signed in to change notification settings - Fork 12
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
chore: fix the navigation #614
base: staging
Are you sure you want to change the base?
Conversation
15442de
to
92895f8
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is not what was asked in rero/rero-ils#3628.
The problem that the back button/browser function sometimes takes us to an editor view, sometimes not is not fixed by this PR.
When a resource is added or modified, it is not always returned to the correct page. The editor now uses the previous url to redirect. * Closes rero/rero-ils#3628. Co-Authored-by: Bertrand Zuchuat <[email protected]>
92895f8
to
4ed680e
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not-blocking: doesn't work for library editor beacuse it is not formly/jsonschema based. But this is not important as it is used very little.
After discussion, we decided to wait on this PR because it has unintended effects on the current workflows for professionnals, for example:
|
When a resource is added or modified, it is not always returned to the correct page. The editor now uses the previous url to redirect.