-
Notifications
You must be signed in to change notification settings - Fork 428
Bump react-mosaic-component from 5.3.0 to 6.0.1 #5851
Bump react-mosaic-component from 5.3.0 to 6.0.1 #5851
Conversation
Bumps [react-mosaic-component](https://github.com/nomcopter/react-mosaic) from 5.3.0 to 6.0.1. - [Release notes](https://github.com/nomcopter/react-mosaic/releases) - [Commits](nomcopter/react-mosaic@v5.3.0...v6.0.1) --- updated-dependencies: - dependency-name: react-mosaic-component dependency-type: direct:development update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
851352f
to
265739c
Compare
Something bad happens when upgrading react-dnd. The drag source is getting prematurely disconnected: This same issue originally happened to me while working on #1849. Because it happened then, I thought it was related to react-dnd/react-dnd#3290, which seemed like the only relevant change in that release. I was hoping that a future release (2 major versions later) would resolve the issue, but it's still happening |
This is blocked on react-dnd/react-dnd#3565. Since there's been no response on that PR we may need to apply the patch ourselves. |
…rn/react-mosaic-component-6.0.1
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
cc @defunctzombie to review patch for react-dnd/react-dnd#3565
…rn/react-mosaic-component-6.0.1
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
If we find ourselves wanting to update this patch I think we should fork react-dnd and use our version. Upstream has no updates and if it ever comes alive we can use upstream again. But we can use the patch until we need to iterate more.
Bumps react-mosaic-component from 5.3.0 to 6.0.1.
Release notes
Sourced from react-mosaic-component's releases.
Commits
74f69ed
v6.0.1163181d
Merge pull request #207 from fvsch/fvsch/import-lodash-functions-explicitly1da3e7c
Fix lodash bare import in OptionalBlueprint.tsxfdfbc10
Add tslint rule forbidding lodash bare importc074f90
v6.0.0cf4f005
Merge pull request #204 from nomcopter/continue-dependency-update2d2d62a
Merge branch 'master' into continue-dependency-updateca33316
Remove event.stopPropagation()8bbc470
Upgrade prettiera4dd544
Downgrade mocha to a version before it knew about ESM...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)