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

chore(deps): update dependency redux-mock-store to v1.5.5 #364

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

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Oct 22, 2024

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
redux-mock-store 1.5.4 -> 1.5.5 age adoption passing confidence

Release Notes

arnaudbenard/redux-mock-store (redux-mock-store)

v1.5.5: - Deprecation

Compare Source

This patch release deprecates the configureStore method, as this package does not align with the Redux team's recommended testing practices. Instead, we recommend testing with a real store.

Testing with a mock store leads to potentially confusing behaviour, such as state not updating when actions are dispatched. Additionally, it's a lot less useful to assert on the actions dispatched rather than the observable state changes.

You can test the entire combination of action creators, reducers, and selectors in a single test, for example:

it('should add a todo', () => {
  const store = makeStore() // a user defined reusable store factory

  store.dispatch(addTodo('Use Redux'))

  expect(selectTodos(store.getState())).toEqual([
    { text: 'Use Redux', completed: false }
  ])
})

This avoids common pitfalls of testing each of these in isolation, such as mocked state shape becoming out of sync with the actual application.

legacy_configureStore

We recognise that for many codebases, migration will be a major effort that some may not be able to allocate time for.
The @deprecated tag is just a visual strikethrough, but some tools will add extra warnings when it is used.

We now have a legacy_configureStore export (similar to legacy_createStore in Redux core) which is the same function but without this tag. You can change any imports to use this if the deprecation notice presents significant issues for you.

- import configureStore from "redux-mock-store"
+ import { legacy_configureStore as configureStore } from "redux-mock-store"

// or

- import { configureStore } from "redux-mock-store"
+ import { legacy_configureStore as configureStore } from "redux-mock-store"

Full Changelog: reduxjs/redux-mock-store@v1.5.4...v1.5.5


Configuration

📅 Schedule: Branch creation - "before 11pm" in timezone America/New_York, Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot enabled auto-merge (rebase) October 22, 2024 23:22
Copy link

codecov bot commented Oct 22, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 100.00%. Comparing base (4581cf8) to head (f50102d).

Additional details and impacted files
@@            Coverage Diff            @@
##            master      #364   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files          109       109           
  Lines         1085      1085           
  Branches       166       166           
=========================================
  Hits          1085      1085           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@renovate renovate bot force-pushed the renovate/redux-mock-store-1.x-lockfile branch 3 times, most recently from ffda6aa to f1d3734 Compare November 5, 2024 17:02
@renovate renovate bot force-pushed the renovate/redux-mock-store-1.x-lockfile branch from f1d3734 to f50102d Compare November 12, 2024 16:10
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.

1 participant