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

feat: upgrade to the single-spa 5.6.0 #203

Merged
merged 2 commits into from
Sep 24, 2020
Merged

Conversation

StyleT
Copy link
Contributor

@StyleT StyleT commented Sep 23, 2020

No description provided.

@@ -1,4 +1,4 @@
import {triggerAppChange} from 'single-spa';
import {triggerAppChange} from './navigationEvents';
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do we have here events setting up twice?
Look at ilc/client line number 1

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nope, due to the cache of the imports. Files are executed only once

@@ -1,3 +1,4 @@
import './client/navigationEvents';
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It is a little bit tricky
I think that would be easy just to import setupEvents here

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The idea is to have single entry point to this "module"

@StyleT StyleT merged commit 34a31b0 into master Sep 24, 2020
@StyleT StyleT deleted the feature/single_spa_update branch September 24, 2020 15:01
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.

3 participants