fix(grid): fix grid prop editConfig is null

[gimmyhehe]

PR

修复用户主动传editConfig为null时报错的问题

PR Checklist

Please check if your PR fulfills the following requirements:

• The commit message follows our Commit Message Guidelines
• Tests for the changes have been added (for bug fixes / features)
• Docs have been added / updated (for bug fixes / features)

PR Type

What kind of change does this PR introduce?

• Bugfix
• Feature
• Code style update (formatting, local variables)
• Refactoring (no functional changes, no api changes)
• Build related changes
• CI related changes
• Documentation content changes
• Other... Please describe:

What is the current behavior?

Issue Number: N/A

What is the new behavior?

Does this PR introduce a breaking change?

• Yes
• No

Other information

Summary by CodeRabbit

• Bug Fixes
  • Enhanced grid row change handling to prevent errors during certain table operations. Improved stability when managing row state in edge cases.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

Walkthrough

Modified the table methods to use safe optional chaining with nullish coalescing when accessing insertChanged from editConfig, preventing errors when editConfig is undefined and ensuring a boolean default value.

Changes

Cohort / File(s)	Summary
Defensive property access packages/vue/src/grid/src/table/src/methods.ts	Replaced direct destructuring of insertChanged from editConfig with optional chaining and nullish coalescing (editConfig?.insertChanged ?? false) to safely handle undefined editConfig

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Poem

🐰 A gentle chain of safety ties,
Where undefined won't catch our eyes,
With coalescing, soft and true,
False defaults see us through! ✨

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly and specifically describes the main fix: addressing the issue when editConfig prop is null, which directly matches the code change that adds safe optional-chaining to prevent errors when editConfig is undefined.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✨ Finishing touches

• 📝 Generate docstrings

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch cgm/editconfig-null

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 3351336 and c6fd6be.

📒 Files selected for processing (1)

• packages/vue/src/grid/src/table/src/methods.ts (1 hunks)

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)

• GitHub Check: PR E2E Test (pnpm test:e2e3)

🔇 Additional comments (1)

packages/vue/src/grid/src/table/src/methods.ts (1)

683-721: LGTM! Correctly handles null editConfig.

The change from destructuring to optional chaining with nullish coalescing properly prevents the error when editConfig is explicitly null. The default value {} on line 684 only applies when this.editConfig is undefined, not null, so the optional chaining at line 685 is necessary. The ?? false ensures insertChanged is always a boolean, which is appropriate for the return logic at line 690.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}