search

coderplanets / coderplanets_web

maybe the most sexiest community for developers based in china, build with React, Mobx/MST, GraphQL, Styled-Components, Rxjs, Ramda ... and ❤️
https://coderplanets.com
GNU General Public License v3.0
336 stars 39 forks source link

chore(deps): bump mobx-react from 7.2.0 to 7.5.2 #1359

Closed dependabot[bot] closed 1 year ago

dependabot[bot] commented 1 year ago

Bumps mobx-react from 7.2.0 to 7.5.2.

Release notes

Sourced from mobx-react's releases.

mobx-react@7.5.2

Patch Changes

mobx-react@7.5.1

Patch Changes

mobx-react@7.5.0

Minor Changes

mobx-react@7.4.0

Minor Changes

  • 4c5e75cd #3382 Thanks @​iChenLei! - replace the deprecated react type definition with recommended type definition

  • bd4b70d8 #3387 Thanks @​mweststrate! - Added experimental / poor man's support for React 18. Fixes #3363, #2526. Supersedes #3005

    • Updated tests, test / build infra, peerDependencies to React 18
    • [breaking icmw upgrading to React 18] Already deprecated hooks like useMutableSource will trigger warnings in React 18, which is correct and those shouldn't be used anymore.
    • [breaking icmw upgrading to React 18] When using React 18, it is important that act is used in unit tests around every programmatic mutation. Without it, changes won't propagate!
    • The React 18 support is poor man's support; that is, we don't do anything yet to play nicely with Suspense features. Although e.g. startTransition basically works, MobX as is doesn't respect the Suspense model and will always reflect the latest state that is being rendered with, so tearing might occur. I think this is in theoretically addressable by using useSyncExternalStore and capturing the current values together with the dependency tree of every component instance. However that isn't included in this pull request 1) it would be a breaking change, whereas the current change is still compatible with React 16 and 17. 2) I want to collect use cases where the tearing leads to problems first to build a better problem understanding. If you run into the problem, please submit an issue describing your scenario, and a PR with a unit tests demonstrating the problem in simplified form. For further discussion see #2526, #3005

Patch Changes

mobx-react@7.3.0

Minor Changes

  • 59b42c28 #3282 Thanks @​urugator! - observer(forwardRef(fn)) no longer generates extra <Observer> element and applies memo correctly

Patch Changes

  • Updated dependencies [59b42c28]:
    • mobx-react-lite@3.3.0

mobx-react@7.2.1

Patch Changes

Commits


Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
dependabot[bot] commented 1 year ago

Looks like mobx-react is up-to-date now, so this is no longer needed.