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.

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

Prevent null on navHistory #1470

Closed
RodriSanchez1 opened this issue Apr 25, 2023 · 1 comment · Fixed by #1489
Closed

Prevent null on navHistory #1470

RodriSanchez1 opened this issue Apr 25, 2023 · 1 comment · Fixed by #1489
Milestone

Comments

@RodriSanchez1
Copy link
Collaborator

RodriSanchez1 commented Apr 25, 2023

image

@RodriSanchez1
Copy link
Collaborator Author

RodriSanchez1 commented May 9, 2023

Update: The bug is created when logout from settings Logout button and login again from the same button without leaving the page.

When the LOGOUT_SUCCES is dispatched, the board reducer is seted to the initial state which is : navHistory: [] and the activeBoardId: null . After login, without leaving the settings page, on Board.reducer LOGIN_SUCCES :

return {
        ...state,
        activeBoardId,
        navHistory: [activeBoardId]
      };

activeBoardId is null. This put a null value on the navHistory.
This bug only occurs when the user doesnt have his own communicator created.

image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants