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 for #2135 #2136

Merged
merged 2 commits into from
Oct 12, 2019
Merged

Fix for #2135 #2136

merged 2 commits into from
Oct 12, 2019

Conversation

xaviergonz
Copy link
Contributor

Rather than using the global state for the action stack checks (which might be uninitialized in older mobx versions) it will just rely on local state.
In theory this means the check will be less effective (since it will only check the stack of actions called using the same mobx version are ok), but less likely to break in multiple mobx version scenarios.

Should fix #2135

@xaviergonz
Copy link
Contributor Author

@mweststrate should this approach be used or the globlal state versioning one?

@mweststrate
Copy link
Member

I think this is ok

@coveralls
Copy link

Coverage Status

Coverage remained the same at 93.388% when pulling 5b39968 on fix-2135 into 92cc3e8 on master.

@xaviergonz xaviergonz merged commit b3ba479 into master Oct 12, 2019
@thecodejack
Copy link

@mweststrate can we please have a patch release of this?

@mweststrate
Copy link
Member

mweststrate commented Oct 18, 2019 via email

@mweststrate mweststrate deleted the fix-2135 branch November 6, 2019 22:51
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.

Why am I getting an invalid action stack error?
5 participants