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

375 复制excel数据到编辑器中格式错乱 #475

Merged
merged 4 commits into from
Dec 26, 2024

Conversation

cycleccc
Copy link
Collaborator

@cycleccc cycleccc commented Dec 26, 2024

Changes Overview

Implementation Approach

Testing Done

Verification Steps

Additional Notes

Checklist

  • I have created a changeset for this PR if necessary.
  • My changes do not break the library.
  • I have added tests where applicable.
  • I have followed the project guidelines.
  • I have fixed any lint issues.

Related Issues

Summary by CodeRabbit

  • New Features

    • Introduced patches for improved functionality in the table and editor modules.
    • Enhanced logic for resizing table columns, allowing for more controlled adjustments.
    • Updated logic for calculating column widths in tables, improving rendering based on cell configurations.
  • Bug Fixes

    • Addressed formatting errors when copying Excel data into the editor.

@cycleccc cycleccc linked an issue Dec 26, 2024 that may be closed by this pull request
Copy link

changeset-bot bot commented Dec 26, 2024

⚠️ No Changeset found

Latest commit: 73e7b6d

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

Copy link
Contributor

coderabbitai bot commented Dec 26, 2024

Walkthrough

The pull request introduces patches for the @wangeditor-next/table-module and @wangeditor-next/editor packages, focusing on improvements to table column resizing and HTML parsing logic. The changes modify how column widths are calculated and constrained during user interactions, enhancing the table editing experience in the text editor by providing more robust width management and rendering strategies.

Changes

File Change Summary
packages/table-module/src/module/column-resize.ts Modified column resizing logic to cap width increases and enforce minimum width constraints
packages/table-module/src/module/parse-elem-html.ts Updated column width calculation strategy, prioritizing tdList over colgroupElments and adjusting default width handling

Poem

🐰 Resize and parse, with rabbit's grace,
Tables dancing in their digital space
Columns stretch, but never too wide
Pixels measured with mathematical pride
A code ballet of width and might! 🏓

Tip

CodeRabbit's docstrings feature is now available as part of our Early Access Program! Simply use the command @coderabbitai generate docstrings to have CodeRabbit automatically generate docstrings for your pull request. We would love to hear your feedback on Discord.


Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share
🪧 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 generate docstrings to generate docstrings for this PR. (Beta)
  • @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

🧹 Nitpick comments (2)
packages/table-module/src/module/parse-elem-html.ts (2)

136-136: Mismatch in code comment for default width

The inline comment says “获取 width,默认为 180” but the code uses || '90' as the default. Update the comment to reflect the correct default of 90.

- // 获取 width,默认为 180
+ // 获取 width,默认为 90

145-148: Handle potential NaN column widths from colgroup

Here, parseInt(col.getAttribute('width'), 10) can yield NaN if the attribute is not present or not a valid number. Consider providing a fallback (e.g., 90) to avoid silently inserting NaN into columnWidths.

-return parseInt(col.getAttribute('width'), 10)
+return parseInt(col.getAttribute('width') || '90', 10)
📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 163b2b3 and f3c5f9f.

📒 Files selected for processing (3)
  • .changeset/smooth-trains-fry.md (1 hunks)
  • packages/table-module/src/module/column-resize.ts (1 hunks)
  • packages/table-module/src/module/parse-elem-html.ts (1 hunks)
✅ Files skipped from review due to trivial changes (1)
  • .changeset/smooth-trains-fry.md
🔇 Additional comments (2)
packages/table-module/src/module/parse-elem-html.ts (1)

131-141: Question the assignment of columnWidths[0] within the loop

Within the forEach(td => ...) block, each td sets columnWidths[0] = width, which continuously overwrites the same index. This could lead to unexpected values if there’s more than one td in the row. Consider pushing width for each iteration instead, or confirm it’s intentional that only the first column’s width is used while additional columns default to 90.

Proposed fix for a typical multi-cell scenario (i.e., pushing widths sequentially rather than always setting index 0):

- columnWidths[0] = width
- for (let i = 1; i < colSpan; i += 1) {
-   columnWidths.push(90)
- }
+ columnWidths.push(width)
+ for (let i = 1; i < colSpan; i += 1) {
+   columnWidths.push(90)
+ }
packages/table-module/src/module/column-resize.ts (1)

136-140: Verify handling of container resizing and multi-user scenarios

The new condition disallows column expansion if remainWidth + newWith exceeds the container width, forcing a fallback to cellWidthWhenMouseDown. This properly prevents oversizing beyond the container. However, if the container is dynamically resized after the mouse down or if multiple users (in real-time collaboration) change widths simultaneously, it might cause unexpected behaviors. Consider listening for container dimension changes in real time or re-checking the container size just before finalizing the new column width.

Would you like a script to search the codebase for container resizing or concurrency checks to ensure alignment with your collaboration flow?

@cycleccc cycleccc merged commit f4e759e into master Dec 26, 2024
2 checks passed
@coderabbitai coderabbitai bot mentioned this pull request Dec 30, 2024
5 tasks
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.

复制excel数据到编辑器中格式错乱
1 participant