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.

Sign up for GitHub

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

Jump to bottom

Bump @dnd-kit/core and @dnd-kit/modifiers in /frontend #841

Closed
wants to merge 1 commit into from
Closed

Bump @dnd-kit/core and @dnd-kit/modifiers in /frontend #841

wants to merge 1 commit into from

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Sep 25, 2023 •
edited
Loading

Bumps @dnd-kit/core and @dnd-kit/modifiers. These dependencies needed to be updated together.
Updates @dnd-kit/core from 4.0.3 to 6.0.8

Release notes

Sourced from @​dnd-kit/core's releases.

@​dnd-kit/core@​6.0.8

Patch Changes

  • #1038 da888ee Thanks @​WillDonohoe! - Fix errors with calls to getComputedStyle in Firefox when destructuring from the window object

@​dnd-kit/core@​6.0.7

Patch Changes

@​dnd-kit/core@​6.0.6

Patch Changes

@​dnd-kit/core@​6.0.5

Patch Changes

@​dnd-kit/core@​6.0.4

Patch Changes

@​dnd-kit/core@​6.0.3

Patch Changes

  • #772 e97cb1f Thanks @​clauderic! - The ARIA live region element used for screen reader announcements is now positioned using position: fixed instead of position: absolute. As of @dnd-kit/core^6.0.0, the live region element is no longer portaled by default into the document.body. This change was introduced in order to fix issues with portaled live regions. However, this change can introduce visual regressions when using absolutely positioned elements, since the live region element is constrained to the stacking and position context of its closest positioned ancestor. Using fixed position ensures the element does not introduce visual regressions.

@​dnd-kit/core@​6.0.2

Patch Changes

  • #769 8e3599f Thanks @​clauderic! - Fixed an issue with the containerNodeRect that is exposed to modifiers having stale properties (top, left, etc.) when its scrollable ancestors were scrolled.

  • #769 53cb962 Thanks @​clauderic! - Fixed a regression with scrollable ancestors detection.

    The scrollable ancestors should be determined by the active node or the over node exclusively. The draggingNode variable shouldn't be used to detect scrollable ancestors since it can be the drag overlay node, and the drag overlay node doesn't have any scrollable ancestors because it is a fixed position element.

@​dnd-kit/core@​6.0.1

Patch Changes

  • #759 e5b9d38 Thanks @​clauderic! - Fixed a regression with the default drop animation of <DragOverlay> for consumers using React 18.

@​dnd-kit/core@​6.0.0

Major Changes

... (truncated)

Changelog

Sourced from @​dnd-kit/core's changelog.

6.0.8

Patch Changes

  • #1038 da888ee Thanks @​WillDonohoe! - Fix errors with calls to getComputedStyle in Firefox when destructuring from the window object

6.0.7

Patch Changes

6.0.6

Patch Changes

6.0.5

Patch Changes

6.0.4

Patch Changes

6.0.3

Patch Changes

  • #772 e97cb1f Thanks @​clauderic! - The ARIA live region element used for screen reader announcements is now positioned using position: fixed instead of position: absolute. As of @dnd-kit/core^6.0.0, the live region element is no longer portaled by default into the document.body. This change was introduced in order to fix issues with portaled live regions. However, this change can introduce visual regressions when using absolutely positioned elements, since the live region element is constrained to the stacking and position context of its closest positioned ancestor. Using fixed position ensures the element does not introduce visual regressions.

6.0.2

Patch Changes

  • #769 8e3599f Thanks @​clauderic! - Fixed an issue with the containerNodeRect that is exposed to modifiers having stale properties (top, left, etc.) when its scrollable ancestors were scrolled.

  • #769 53cb962 Thanks @​clauderic! - Fixed a regression with scrollable ancestors detection.

    The scrollable ancestors should be determined by the active node or the over node exclusively. The draggingNode variable shouldn't be used to detect scrollable ancestors since it can be the drag overlay node, and the drag overlay node doesn't have any scrollable ancestors because it is a fixed position element.

6.0.1

... (truncated)

Commits

Updates @dnd-kit/modifiers from 4.0.0 to 6.0.0

Release notes

Sourced from @​dnd-kit/modifiers's releases.

@​dnd-kit/modifiers@​6.0.0

Patch Changes

@​dnd-kit/modifiers@​5.0.0

Minor Changes

  • #567 cd3adf3 Thanks @​clauderic! - Update modifiers to use draggingNodeRect instead of activeNodeRect. Modifiers should be based on the rect of the node being dragged, whether it is the draggable node or drag overlay node.

  • #518 6310227 Thanks @​clauderic! - Major internal refactor of measuring and collision detection.

    Summary of changes

    Previously, all collision detection algorithms were relative to the top and left points of the document. While this approach worked in most situations, it broke down in a number of different use-cases, such as fixed position droppable containers and trying to drag between containers that had different scroll positions.

    This new approach changes the frame of comparison to be relative to the viewport. This is a major breaking change, and will need to be released under a new major version bump.

    Breaking changes:

    • By default, @dnd-kit now ignores only the transforms applied to the draggable / droppable node itself, but considers all the transforms applied to its ancestors. This should provide the right balance of flexibility for most consumers.
      • Transforms applied to the droppable and draggable nodes are ignored by default, because the recommended approach for moving items on the screen is to use the transform property, which can interfere with the calculation of collisions.
      • Consumers can choose an alternate approach that does consider transforms for specific use-cases if needed by configuring the measuring prop of . Refer to the example.
    • Reduced the number of concepts related to measuring from ViewRect, LayoutRect to just a single concept of ClientRect.
      • The ClientRect interface no longer holds the offsetTop and offsetLeft properties. For most use-cases, you can replace offsetTop with top and offsetLeft with left.
      • Replaced the following exports from the @dnd-kit/core package with getClientRect:
        • getBoundingClientRect
        • getViewRect
        • getLayoutRect
        • getViewportLayoutRect
    • Removed translatedRect from the SensorContext interface. Replace usage with collisionRect.
    • Removed activeNodeClientRect on the DndContext interface. Replace with activeNodeRect.

Patch Changes

Changelog

Sourced from @​dnd-kit/modifiers's changelog.

6.0.0

Patch Changes

5.0.0

Minor Changes

  • #567 cd3adf3 Thanks @​clauderic! - Update modifiers to use draggingNodeRect instead of activeNodeRect. Modifiers should be based on the rect of the node being dragged, whether it is the draggable node or drag overlay node.

  • #518 6310227 Thanks @​clauderic! - Major internal refactor of measuring and collision detection.

    Summary of changes

    Previously, all collision detection algorithms were relative to the top and left points of the document. While this approach worked in most situations, it broke down in a number of different use-cases, such as fixed position droppable containers and trying to drag between containers that had different scroll positions.

    This new approach changes the frame of comparison to be relative to the viewport. This is a major breaking change, and will need to be released under a new major version bump.

    Breaking changes:

    • By default, @dnd-kit now ignores only the transforms applied to the draggable / droppable node itself, but considers all the transforms applied to its ancestors. This should provide the right balance of flexibility for most consumers.
      • Transforms applied to the droppable and draggable nodes are ignored by default, because the recommended approach for moving items on the screen is to use the transform property, which can interfere with the calculation of collisions.
      • Consumers can choose an alternate approach that does consider transforms for specific use-cases if needed by configuring the measuring prop of . Refer to the example.
    • Reduced the number of concepts related to measuring from ViewRect, LayoutRect to just a single concept of ClientRect.
      • The ClientRect interface no longer holds the offsetTop and offsetLeft properties. For most use-cases, you can replace offsetTop with top and offsetLeft with left.
      • Replaced the following exports from the @dnd-kit/core package with getClientRect:
        • getBoundingClientRect
        • getViewRect
        • getLayoutRect
        • getViewportLayoutRect
    • Removed translatedRect from the SensorContext interface. Replace usage with collisionRect.
    • Removed activeNodeClientRect on the DndContext interface. Replace with activeNodeRect.

Patch Changes

Commits
  • d5838e6 Version Packages
  • d1a2df9 Version Packages
  • cd3adf3 Update modifiers to use draggingNodeRect instead of activeNodeRect (#567)
  • f3ad20d Refactor CollisionDetection to return an array of Collisions (#558)
  • 9719ab8 Refactor measuring and collision detection
  • See full diff in compare view

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 show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @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 dependabot bot force-pushed the dependabot/npm_and_yarn/frontend/dnd-kit/core-and-dnd-kit/modifiers-6.0.8 branch 2 times, most recently from aaa81d0 to b874e7f Compare October 3, 2023 16:52
@dependabot @claire2212
Bump @dnd-kit/core and @dnd-kit/modifiers in /frontend
d2f8275 
Bumps [@dnd-kit/core](https://github.com/clauderic/dnd-kit/tree/HEAD/packages/core) and [@dnd-kit/modifiers](https://github.com/clauderic/dnd-kit/tree/HEAD/packages/modifiers). These dependencies needed to be updated together.

Updates `@dnd-kit/core` from 4.0.3 to 6.0.8
- [Release notes](https://github.com/clauderic/dnd-kit/releases)
- [Changelog](https://github.com/clauderic/dnd-kit/blob/master/packages/core/CHANGELOG.md)
- [Commits](https://github.com/clauderic/dnd-kit/commits/@dnd-kit/[email protected]/packages/core)

Updates `@dnd-kit/modifiers` from 4.0.0 to 6.0.0
- [Release notes](https://github.com/clauderic/dnd-kit/releases)
- [Changelog](https://github.com/clauderic/dnd-kit/blob/master/packages/modifiers/CHANGELOG.md)
- [Commits](https://github.com/clauderic/dnd-kit/commits/@dnd-kit/[email protected]/packages/modifiers)

---
updated-dependencies:
- dependency-name: "@dnd-kit/core"
  dependency-type: direct:production
  update-type: version-update:semver-major
- dependency-name: "@dnd-kit/modifiers"
  dependency-type: direct:production
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <[email protected]>
@claire2212 claire2212 force-pushed the dependabot/npm_and_yarn/frontend/dnd-kit/core-and-dnd-kit/modifiers-6.0.8 branch from b874e7f to d2f8275 Compare October 12, 2023 12:00
@claire2212 claire2212 closed this Oct 23, 2023
@dependabot @github
Copy link
Contributor Author

dependabot bot commented on behalf of github Oct 23, 2023

OK, I won't notify you again about this release, but will get in touch when a new version is available. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.

@dependabot dependabot bot deleted the dependabot/npm_and_yarn/frontend/dnd-kit/core-and-dnd-kit/modifiers-6.0.8 branch October 23, 2023 07:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees

@thoomasbro thoomasbro

@claire2212 claire2212

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@thoomasbro @claire2212