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 slate to v0.110.2 #116

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

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Aug 11, 2024

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
slate ^0.72.0 -> ^0.110.0 age adoption passing confidence
slate ^0.72.0 -> ^0.72.0 || ^0.110.0 age adoption passing confidence

Release Notes

ianstormtaylor/slate (slate)

v0.110.2

Compare Source

Patch Changes

v0.103.0

Compare Source

Minor Changes
  • #​5621 d271c4be Thanks @​felixfeng33! - Add a shouldMergeNodesRemovePrevNode editor method to control when Transforms.mergeNodes should remove the previous node rather than carrying out a merge operation.
Patch Changes

v0.102.0

Compare Source

Patch Changes

v0.101.5

Compare Source

Patch Changes

v0.101.4

Compare Source

Patch Changes

v0.101.1

Compare Source

Patch Changes

v0.100.0

Compare Source

Minor Changes

v0.94.1

Compare Source

Patch Changes
  • #​5415 01f0210b Thanks @​zbeyens! - Editor.insertFragment, Editor.insertNode, Editor.insertText now accept options.
    For all insert methods, the default location is now the editor selection if at is not defined, or the end of document if editor.selection is not defined.

v0.94.0

Compare Source

v0.93.0

Compare Source

v0.91.4

Compare Source

Patch Changes

v0.91.3

Compare Source

Patch Changes
  • #​5295 84f811a7 Thanks @​zbeyens! - New editor method that can be overridden to control when the normalization should stop. Default behavior (unchanged) is to throw an error when it iterates over 42 times the dirty paths length.

    shouldNormalize: ({
      iteration,
      dirtyPaths,
      operation,
    }: {
      iteration: number
      dirtyPaths: Path[]
      operation?: Operation
    }) => boolean
    • editor.onChange signature change: (options?: { operation?: Operation }) => void where operation is triggering the function.
    • editor.normalizeNode signature change: (entry: NodeEntry, options?: { operation?: Operation }) => void where operation is triggering the function.
    • EditorNormalizeOptions new option operation?: Operation where operation is triggering the function.

v0.91.1

Compare Source

Patch Changes

v0.90.0

Compare Source

v0.88.1

Compare Source

Patch Changes

v0.87.0

Compare Source

v0.86.0

Compare Source

Patch Changes

v0.85.0

Compare Source

Minor Changes

v0.84.0

Compare Source

Minor Changes

v0.82.1

Compare Source

Patch Changes

v0.82.0

Compare Source

Patch Changes
  • #​4988 fbab6331 Thanks @​BitPhinix! - Android input handling rewrite, replace composition insert prefixes with decoration based mark placeholders

v0.81.3

Compare Source

v0.81.1

Compare Source

Patch Changes
  • #​5015 9ae37287 Thanks @​tithanayut! - Fix deleteBackward behavior for Thai script where deleting N character(s) backward should delete
    N code point(s) instead of an entire grapheme cluster

v0.81.0

Compare Source

Minor Changes

v0.80.0

Compare Source

Minor Changes
Patch Changes

v0.78.0

Compare Source

Minor Changes

v0.77.2

Compare Source

Patch Changes

v0.77.0

Compare Source

Patch Changes

v0.76.1

Compare Source

Patch Changes

v0.76.0

Compare Source

Minor Changes
  • #​4873 20acca4b Thanks @​bryanph! - A different behavior for inserting a soft break with shift+enter is quite common in rich text editors. Right now you have to do this in onKeyDown which is not so nice. This adds a separate insertSoftBreak method on the editor instance that gets called when a soft break is inserted. This maintains the current default behavior for backwards compatibility (it just splits the block). But at least you can easily overwrite it now.

    If you rely on overwriting editor.insertBreak for extra behavior for soft breaks this might be a breaking change for you and you should overwrite editor.insertSoftBreak instead.

Patch Changes

v0.75.0

Compare Source

Patch Changes

v0.73.1

Compare Source

Patch Changes

v0.73.0

Compare Source

Minor Changes

v0.72.8

Compare Source

Patch Changes

v0.72.3

Compare Source

Patch Changes

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

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 these updates again.


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

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

Copy link
Contributor

coderabbitai bot commented Aug 11, 2024

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Walkthrough

The overall change involves updating the version specifications for the slate dependency across multiple packages. The primary modification expands the compatibility range from a fixed version, ^0.72.0, to a broader range that includes ^0.72.0 || ^0.103.0. This allows developers to utilize newer features and improvements from the slate library while maintaining support for existing implementations.

Changes

Files Change Summary
packages/basic-modules/package.json, packages/code-highlight/package.json, packages/core/package.json, packages/list-module/package.json, packages/table-module/package.json, packages/upload-image-module/package.json, packages/video-module/package.json Updated slate dependency from "^0.72.0" to `"^0.72.0
packages/editor/package.json Upgraded slate dependency from "^0.72.0" to "^0.103.0", indicating a transition to a newer version with enhancements.

Poem

🌼 In the meadow where rabbits play,
New versions dance and sway!
Slate's range now broad and bright,
A hop, a skip, a joyful flight!
Code and bunnies leap with glee,
For changes bring new harmony! 🐇✨


🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 5791fcd and 152cfcb.

Files ignored due to path filters (1)
  • yarn.lock is excluded by !**/yarn.lock, !**/*.lock
Files selected for processing (8)
  • packages/basic-modules/package.json (1 hunks)
  • packages/code-highlight/package.json (1 hunks)
  • packages/core/package.json (1 hunks)
  • packages/editor/package.json (1 hunks)
  • packages/list-module/package.json (1 hunks)
  • packages/table-module/package.json (1 hunks)
  • packages/upload-image-module/package.json (1 hunks)
  • packages/video-module/package.json (1 hunks)
Additional comments not posted (8)
packages/list-module/package.json (1)

45-45: Approved: Broadened slate version compatibility.

The update to the slate version in peerDependencies expands compatibility and aligns with the PR objectives.

packages/video-module/package.json (1)

48-48: Approved: Broadened slate version compatibility.

The update to the slate version in peerDependencies expands compatibility and aligns with the PR objectives.

packages/table-module/package.json (1)

49-49: Approved: Broadened slate version compatibility.

The update to the slate version in peerDependencies expands compatibility and aligns with the PR objectives.

packages/code-highlight/package.json (1)

45-45: Approved: Expanded version range for slate.

The change to peerDependencies allows compatibility with a broader range of slate versions. Ensure that this does not introduce conflicts with other dependencies in your project.

packages/upload-image-module/package.json (1)

49-49: Approved: Expanded version range for slate.

The change to peerDependencies allows compatibility with a broader range of slate versions. Ensure that this does not introduce conflicts with other dependencies in your project.

packages/basic-modules/package.json (1)

47-47: Approved: Expanded version range for slate.

The change to peerDependencies allows compatibility with a broader range of slate versions. Ensure that this does not introduce conflicts with other dependencies in your project.

packages/core/package.json (1)

55-55: Dependency version update approved.

The update to the slate dependency version range allows for greater flexibility and access to new features. Ensure that the codebase is compatible with the newer version of slate.

packages/editor/package.json (1)

70-70: Dependency version update approved.

The update to the slate dependency version to ^0.103.0 should provide access to new features and improvements. Ensure that the codebase is compatible with this newer version.

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 152cfcb and 3d5cc58.

Files ignored due to path filters (1)
  • yarn.lock is excluded by !**/yarn.lock, !**/*.lock
Files selected for processing (8)
  • packages/basic-modules/package.json (1 hunks)
  • packages/code-highlight/package.json (1 hunks)
  • packages/core/package.json (1 hunks)
  • packages/editor/package.json (1 hunks)
  • packages/list-module/package.json (1 hunks)
  • packages/table-module/package.json (1 hunks)
  • packages/upload-image-module/package.json (1 hunks)
  • packages/video-module/package.json (1 hunks)
Additional comments not posted (8)
packages/list-module/package.json (1)

45-45: Dependency version update approved.

The change in the slate dependency version from "^0.72.0" to "^0.72.0 || ^0.103.0" is a good practice for maintaining compatibility with both older and newer versions. This ensures that the package can leverage new features and improvements while still supporting projects that depend on the older version.

packages/video-module/package.json (1)

48-48: Dependency version update approved.

Updating the slate dependency version to "^0.72.0 || ^0.103.0" in this package as well ensures consistency across different modules of the project. This change supports the use of both older and newer features of slate, enhancing the module's flexibility and compatibility.

packages/table-module/package.json (1)

49-49: Dependency version update approved.

The update to "^0.72.0 || ^0.103.0" for the slate dependency in this module aligns with the updates in other modules, promoting uniformity and compatibility across the project. This strategic update facilitates the adoption of new features from slate while maintaining support for the existing version.

packages/code-highlight/package.json (1)

45-45: Dependency Version Update Approved

The update to the slate dependency version from "^0.72.0" to "^0.72.0 || ^0.103.0" is approved as it enhances flexibility in dependency management. This change allows the module to leverage new features and improvements in slate while maintaining support for the older version.

Please ensure that the module is tested with both versions of slate to verify compatibility. This can be done by setting up automated tests or manual checks.

packages/upload-image-module/package.json (1)

49-49: Dependency Version Update Approved

The update to the slate dependency version from "^0.72.0" to "^0.72.0 || ^0.103.0" is approved. This change broadens the compatibility range, allowing the module to function with both older and newer versions of slate.

Please ensure that the module is tested with both versions of slate to verify compatibility. This can be done by setting up automated tests or manual checks.

packages/basic-modules/package.json (1)

47-47: Dependency Version Update Approved

The update to the slate dependency version from "^0.72.0" to "^0.72.0 || ^0.103.0" is approved. This change allows the basic modules to utilize features from both older and newer versions of slate.

Please ensure that the basic modules are tested with both versions of slate to verify compatibility. This can be done by setting up automated tests or manual checks.

packages/core/package.json (1)

55-55: Dependency version update approved.

The update to "slate": "^0.72.0 || ^0.103.0" is approved as it broadens the range of acceptable versions, allowing for flexibility in using features from both versions. However, it's crucial to ensure that the project's codebase is compatible with both versions to avoid potential runtime issues.

packages/editor/package.json (1)

70-70: Dependency version update approved.

The update to "slate": "^0.103.0" is approved as it allows the project to leverage new features and improvements from the latest version of slate. It is important to verify that there are no breaking changes affecting the project's existing functionality.

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 3d5cc58 and c2aa44a.

Files ignored due to path filters (1)
  • yarn.lock is excluded by !**/yarn.lock, !**/*.lock
Files selected for processing (8)
  • packages/basic-modules/package.json (1 hunks)
  • packages/code-highlight/package.json (1 hunks)
  • packages/core/package.json (1 hunks)
  • packages/editor/package.json (1 hunks)
  • packages/list-module/package.json (1 hunks)
  • packages/table-module/package.json (1 hunks)
  • packages/upload-image-module/package.json (1 hunks)
  • packages/video-module/package.json (1 hunks)
Files skipped from review due to trivial changes (4)
  • packages/basic-modules/package.json
  • packages/code-highlight/package.json
  • packages/list-module/package.json
  • packages/video-module/package.json
Files skipped from review as they are similar to previous changes (3)
  • packages/core/package.json
  • packages/table-module/package.json
  • packages/upload-image-module/package.json
Additional comments not posted (1)
packages/editor/package.json (1)

70-70: Dependency version update looks good, but ensure compatibility and test thoroughly.

The slate dependency version update from ^0.72.0 to ^0.103.0 is approved. However, please note the following:

  • Review the release notes carefully to understand the changes, especially any breaking changes that might require adjustments in the codebase.
  • Thoroughly test the editor functionality to ensure compatibility with the new version and catch any potential issues early.

To verify compatibility, consider running the following tests:

  1. Unit tests: Ensure that the existing unit tests pass with the new slate version. Update the tests if necessary.
  2. Integration tests: Test the integration of the editor with other components and ensure that the editor behaves as expected.
  3. Manual testing: Perform manual testing of the editor to cover various scenarios and edge cases. Pay special attention to the areas highlighted in the release notes.

If you encounter any issues during testing, please document them and consider rolling back the update or making necessary adjustments in the codebase.

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between c2aa44a and 8b79c64.

Files ignored due to path filters (1)
  • yarn.lock is excluded by !**/yarn.lock, !**/*.lock
Files selected for processing (8)
  • packages/basic-modules/package.json (1 hunks)
  • packages/code-highlight/package.json (1 hunks)
  • packages/core/package.json (1 hunks)
  • packages/editor/package.json (1 hunks)
  • packages/list-module/package.json (1 hunks)
  • packages/table-module/package.json (1 hunks)
  • packages/upload-image-module/package.json (1 hunks)
  • packages/video-module/package.json (1 hunks)
Files skipped from review due to trivial changes (6)
  • packages/basic-modules/package.json
  • packages/code-highlight/package.json
  • packages/core/package.json
  • packages/list-module/package.json
  • packages/upload-image-module/package.json
  • packages/video-module/package.json
Files skipped from review as they are similar to previous changes (1)
  • packages/table-module/package.json
Additional comments not posted (1)
packages/editor/package.json (1)

70-70: Dependency version update looks good, but review the release notes and test the changes.

The slate dependency version has been updated from ^0.72.0 to ^0.103.0, which is a significant upgrade. This may include new features, improvements, and bug fixes, but it may also include breaking changes.

  • Review the release notes for slate version 0.103.0 to understand the changes and their impact on the codebase.
  • Test the changes thoroughly to ensure that the upgrade does not introduce any issues or regressions.

@renovate renovate bot force-pushed the renovate/slate-0.x branch 9 times, most recently from c418754 to 45c3495 Compare September 9, 2024 02:32
@renovate renovate bot force-pushed the renovate/slate-0.x branch 3 times, most recently from 87dea07 to a730186 Compare September 14, 2024 14:55
@renovate renovate bot force-pushed the renovate/slate-0.x branch 3 times, most recently from 123639e to 16a8cb0 Compare September 23, 2024 06:23
@renovate renovate bot force-pushed the renovate/slate-0.x branch 6 times, most recently from 555c0cb to 0102259 Compare November 13, 2024 12:05
@renovate renovate bot force-pushed the renovate/slate-0.x branch 17 times, most recently from 00530f8 to 1be0964 Compare November 20, 2024 09:34
@renovate renovate bot force-pushed the renovate/slate-0.x branch 4 times, most recently from 4a3435c to 8f3ce93 Compare November 26, 2024 08:00
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.

0 participants