Skip to content

Conversation

@BenLorantfy
Copy link
Collaborator

No description provided.

- Copy code and tests from rbp to this library
- Create API: `createInjectorsEnhancer` (new), `injectSaga`, `useInjectSaga`, `injectReducer`, `useInjectReducer`, `forceReducerReload` (new), `SagaInjectionModes`
- Setup jest
- Setup babel
- Committed `package-lock.json` file
- Ensure lodash imports aren't importing all of lodash
- Remove props from being forwarded to saga when using `injectSaga`
@BenLorantfy
Copy link
Collaborator Author

I wonder if we should do a merge commit instead of squash merge dev -> master? Just so we maintain the history?

@julienben julienben changed the title merge dev into master Merge dev into master Sep 19, 2019
@julienben
Copy link
Member

julienben commented Sep 19, 2019

Yes, we can do that. (Not that we wouldn't truly lose the commit history. The dev branch is sticking around ;)

Also, this is your 1.0 release. It needs a release to go with it.

@BenLorantfy
Copy link
Collaborator Author

Sure thing, do I create the release before or after we merge this?

@julienben
Copy link
Member

I believe it goes in this order:

  • Merge dev into master
  • Create a release
  • Publish to npm

Maybe take a look at an article like this to make sure we covered everything?

(Also, I enabled merge commits. Let's try to remember to use them only for merging dev into master.)

@BenLorantfy
Copy link
Collaborator Author

Ok, sounds good. If you can approve this I can merge and create the release.

@BenLorantfy BenLorantfy merged commit ed31c50 into master Sep 23, 2019
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