docs(expanding): clarify description of autoResetExpanded setting

[flawlessv]

🎯 Changes

✅ Checklist

• [x] I have followed the steps in the Contributing guide.
• [x] I have tested this code locally with pnpm test:pr.

🚀 Release Impact

• [x] This change affects published code, and I have generated a changeset.
• [x] This change is docs/CI/dev-only (no release).

Summary by CodeRabbit

• Documentation
  • Clarified the behavior of autoResetExpanded: the reset is described as occurring when the overall table state changes, rather than when only the expanding state changes.
  • Improved wording to reduce confusion and align the description with actual behavior.
  • No functional changes; this is a documentation-only update to enhance accuracy and user understanding.

[changeset-bot[bot]]

⚠️ No Changeset found

Latest commit: 02ee72b0e8dfaaac30cc210b5aa63d5042313d7d

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.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

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

[coderabbitai[bot]]

Walkthrough

Documentation text updated in docs/api/features/expanding.md, clarifying that autoResetExpanded triggers on overall table state changes rather than expanding state changes. No code or behavior changes.

Changes

Cohort / File(s)	Summary
Docs update docs/api/features/expanding.md	Revised description: autoResetExpanded resets on table state changes; clarified wording only, no logic changes.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

I twitch my ears at docs so neat,
A tiny tweak, a tidy treat.
No code to chase, no bugs to mend,
Just clearer trails from end to end.
Tap-tap—approved with happy feet! 🐇✨

Pre-merge checks and finishing touches

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Description Check	⚠️ Warning	The pull request description is missing critical information in the required "🎯 Changes" section. While all three major sections of the template are present and the checklist items are marked, the Changes section contains no description of what modifications were made or the motivation behind them. This section is essential for understanding the purpose of the PR. Additionally, based on the raw summary showing this is a documentation-only change to docs/api/features/expanding.md, the Release Impact section appears to have an inconsistency: the author checked "affects published code" but this appears to be a docs-only change that should instead have the "docs/CI/dev-only" option checked.	The author should fill in the "🎯 Changes" section with a description of what was changed and why. They should explain that the PR clarifies the documentation for the autoResetExpanded setting. Additionally, the Release Impact section should be corrected to reflect that this is a documentation-only change by checking the "docs/CI/dev-only" option instead of the "affects published code" option, unless a changeset was genuinely created for a doc-only change.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Title Check	✅ Passed	The title clearly indicates that this PR updates the documentation for the autoResetExpanded setting in the expanding feature, using conventional commit style and omitting unnecessary details so that reviewers can quickly identify the purpose of the change.
Docstring Coverage	✅ Passed	No functions found in the changes. Docstring coverage check skipped.

✨ Finishing touches

• [ ] 📝 Generate docstrings

🧪 Generate unit tests (beta)

• [ ] Create PR with unit tests
• [ ] Post copyable unit tests in a comment

---

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.}