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

Include dispatchPalette by default in the rootDispatcher #123

Closed
adrw opened this issue Feb 1, 2019 · 0 comments
Closed

Include dispatchPalette by default in the rootDispatcher #123

adrw opened this issue Feb 1, 2019 · 0 comments
Labels
bug Something isn't working palette Palette Example Tab

Comments

@adrw
Copy link
Collaborator

adrw commented Feb 1, 2019

Currently confusion how to wire up dispatchPalette whether it is supposed to be included in the rootDispatcher or not.

@adrw adrw added bug Something isn't working palette Palette Example Tab labels Feb 1, 2019
adrw added a commit that referenced this issue Feb 7, 2019
* Release `0.1.3-19` to fix `@misk/core` failed artifact in `0.1.3-16`
* Use as stable `0.1.3` release
* Start new prerelease sequence at `0.1.4-1`
* latest: `0.1.3`
* alpha: `0.1.4-1`
* [CLOSES #3] `deyarn` all `@misk/` packages, `Dockerfile`, and releasing flow
* [CLOSES #145] Add mandatory `ci-build` to `prepare` before any NPM Publish for all `@misk` packages
* [#123] Finish releasing updates to SimpleNetwork to prefix all dispatch functions and prevent function name collisions in `rootDispatcher`
* [CLOSES #147] Manually set tsconfig.json for all @misk/ packages to fix CI builds
@adrw adrw closed this as completed in 4eebf32 Feb 21, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working palette Palette Example Tab
Projects
None yet
Development

No branches or pull requests

1 participant