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

fix: don't call getCurrentRoute if nav isn't ready #1036

Merged
merged 1 commit into from
Nov 27, 2023

Conversation

acezard
Copy link
Contributor

@acezard acezard commented Nov 27, 2023

This will removes error logs at app start when jsCozyInjection
was trying to get routeName too fast in the app cycle.
Now it will go through the getCurrentRouteName facade
which handles non-ready nav objects.
Also remove unused injections linked to navigation in useGlobalAppState

This will removes error logs at app start when jsCozyInjection
was trying to get routeName too fast in the app cycle.
Now it will go through the getCurrentRouteName facade
which handles non-ready nav objects.
Also remove unused injections linked to navigation in useGlobalAppState
@zatteo
Copy link
Contributor

zatteo commented Nov 27, 2023

Nothing to do, but Also remove unused injections linked to navigation in useGlobalAppState could have been another commit.

@acezard acezard merged commit a9ff7f4 into master Nov 27, 2023
1 check passed
@acezard acezard deleted the fix--don't-call-getCurrentRoute-if-nav-isn't-ready branch November 27, 2023 10:54
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 this pull request may close these issues.

2 participants