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

Move commandListener callbacks outside of render cycle #1544

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

jamonholmgren
Copy link
Member

The commandListener callbacks were running during the dispatch, which breaks React since it's during a render cycle.

This moves it outside of the dispatch call.

Fixes #1542.

  • yarn build-and-test:local passes

Also I'm going to kill this Redux-ish state management system and move to something closer to MobX or Legend State. It's awful to work with.

@@ -135,12 +135,15 @@ export function reducer(state: State, action: Action) {
return
}

draftState.commandListeners.forEach((cl) => cl(action.payload))
Copy link
Member Author

Choose a reason for hiding this comment

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

This is now on line 217 below.

Copy link
Contributor

@frankcalise frankcalise left a comment

Choose a reason for hiding this comment

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

Great stuff, this has been borked for a while I think!

@jamonholmgren
Copy link
Member Author

@joshuayoes How do I release using the new system?

@frankcalise
Copy link
Contributor

@jamonholmgren we built this cool thing called IR docs

https://docs.infinite.red/reactotron/contributing/releasing/

@jamonholmgren
Copy link
Member Author

@frankcalise I actually read that, believe it or not ... but I don't know if there's a format for the commit messages to get picked up by the release notes / changelog.

@frankcalise
Copy link
Contributor

fair, judging by the merged PRs it looks to be the same as Ignite

@joshuayoes
Copy link
Contributor

@jamonholmgren you make a change in the workspace you want to release and the use semantic version keywords in your squash commit title: feat, fix, or chore

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