chore: fix 4626 error documentations

[kevzzsk]

PR Checklist

• Tests
• Documentation
• Changeset entry (run npx changeset add)

[changeset-bot]

⚠️ No Changeset found

Latest commit: 854d383

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]

Walkthrough

This change updates parameter naming in two error declarations within the ERC4626 contract. The errors ERC4626ExceededMaxWithdraw and ERC4626ExceededMaxRedeem have their first parameter renamed from address receiver to address owner. The underlying parameter types remain unchanged (address, uint256, uint256). No functional logic is altered; this is a terminology adjustment to the public error interface.

Suggested labels

typo

Pre-merge checks and finishing touches

❌ Failed checks (1 warning, 1 inconclusive)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%.	You can run @coderabbitai generate docstrings to improve docstring coverage.
Description Check	❓ Inconclusive	The PR description provided by the author is essentially a template with no actual content—it consists only of uncompleted placeholders and a partially filled checklist. While the PR title ("fix 4626 error documentations") suggests some relevance to the changeset, the description body itself is extremely vague and generic, containing no substantive information about what was changed or why. This makes it difficult to conclusively determine whether the description is meaningfully related to the changeset or represents an unfinished submission.	The author should provide an actual description of the changes, explaining what was updated in the ERC4626 error documentation (specifically that parameter names were changed from "receiver" to "owner") and the rationale for these changes. Adding substantive description content will remove ambiguity and provide reviewers with clear context about the PR's intent.

✅ Passed checks (1 passed)

Check name	Status	Explanation
Title Check	✅ Passed	The title "chore: fix 4626 error documentations" directly relates to the main change in the pull request, which involves updating the ERC4626 error declarations by changing parameter names from "receiver" to "owner" in two error definitions. The title is concise, specific to the ERC4626 contract and its error handling, and clearly communicates the nature of the change to someone scanning the repository history. The phrasing accurately captures the focus on fixing error-related declarations in the 4626 contract.

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

[ernestognw]

We don't need a changeset since this doesn't change functionality