-
Notifications
You must be signed in to change notification settings - Fork 31
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
Bug/225 browser back button not navigating in app #325
Conversation
This pull request introduces 1 alert and fixes 1 when merging 5035e38 into 140e818 - view on LGTM.com new alerts:
fixed alerts:
|
This pull request fixes 1 alert when merging 09c75ab into 140e818 - view on LGTM.com fixed alerts:
|
This pull request fixes 1 alert when merging ca00ddc into 140e818 - view on LGTM.com fixed alerts:
|
This pull request fixes 1 alert when merging 2fdcb39 into 140e818 - view on LGTM.com fixed alerts:
|
This pull request fixes 1 alert when merging 031418b into dbe5ed9 - view on LGTM.com fixed alerts:
|
This pull request fixes 1 alert when merging 0408f0b into dbe5ed9 - view on LGTM.com fixed alerts:
|
This pull request fixes 1 alert when merging 5d4b478 into 93b8938 - view on LGTM.com fixed alerts:
|
This pull request fixes 1 alert when merging 4bd1a5b into 93b8938 - view on LGTM.com fixed alerts:
|
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.
Great job in cleaning up cognitive complexity and such along the way! 🥇 This looks good, but I still think we should find a way to solve the usability issue you noted in the initial description - I'm not sure we should be releasing this early at a stage where it causes (apparent) app crashes when clicking the browser back button in some apps.
src/altinn-app-frontend/src/common/hooks/useFormLayoutHistory.ts
Outdated
Show resolved
Hide resolved
src/altinn-app-frontend/src/common/hooks/useFormLayoutHistory.ts
Outdated
Show resolved
Hide resolved
This pull request introduces 3 alerts and fixes 1 when merging 514915b into 93b8938 - view on LGTM.com new alerts:
fixed alerts:
|
514915b
to
f75450d
Compare
This pull request introduces 3 alerts and fixes 1 when merging f75450d into 93b8938 - view on LGTM.com new alerts:
fixed alerts:
|
f75450d
to
f3ce986
Compare
This pull request introduces 3 alerts and fixes 1 when merging f3ce986 into 93b8938 - view on LGTM.com new alerts:
fixed alerts:
|
Refactor: split code in useFormLayoutHistory to smaller chunks
f3ce986
to
6cbe77b
Compare
This pull request introduces 3 alerts when merging 6cbe77b into a5f1f8f - view on LGTM.com new alerts:
|
Kudos, SonarCloud Quality Gate passed! |
Closing this, but keeping the branch for a while. The changes here are similar to #451, which we intend to keep (but have to rewrite to keep up with the ever-changing main). |
Description
I changed the behavior of how the form url changes where it now puts the page id at he end of the route.
By doing so we get to listen to history-changes and re-render the Form component based on the page id inside the formLayout.
Tested in Firefox.
Related Issue(s)
Verification
NOTE
The below steps (in Norwegian) do reproduce am error. However, the issue seems to be related to not being able to access pages after the allowed pages after the page order has been updated or switching layout sets: