fix: correct comment to reference setGrantDelay

[ANtutov]

f.selector == sig:setGrantDelay(uint64,uint32).selector so setTargetAdminDelay -> setGrantDelay

[changeset-bot]

⚠️ No Changeset found

Latest commit: 2d03307

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

A comment in the getRoleGrantDelayChangeCall rule within fv/specs/AccessManager.spec was updated to reference setGrantDelay(uint64,uint32) instead of setTargetAdminDelay. The modification affects only documentation text and introduces no functional or control-flow changes. All existing conditionals and assertions remain unchanged, and no public or exported entities were modified.

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately summarizes the main change: correcting a comment to reference setGrantDelay instead of setTargetAdminDelay in the AccessManager specification.
Description check	✅ Passed	The description is directly related to the changeset, explaining the specific rationale for the comment correction by referencing the function selector comparison.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✨ Finishing touches

🧪 Generate unit tests (beta)

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

---

📜 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 4a4a606 and 2d03307.

📒 Files selected for processing (1)

• fv/specs/AccessManager.spec (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). (6)

• GitHub Check: slither
• GitHub Check: coverage
• GitHub Check: tests-foundry
• GitHub Check: tests
• GitHub Check: tests-upgradeable
• GitHub Check: halmos

🔇 Additional comments (1)

fv/specs/AccessManager.spec (1)

592-593: Comment correction is accurate and consistent with the code.

The updated comment on line 592 now correctly references setGrantDelay, which aligns with the selector check on line 593: f.selector == sig:setGrantDelay(uint64,uint32).selector. This matches the rule's purpose of verifying state transitions for getRoleGrantDelay and is consistent with similar patterns elsewhere in the file (e.g., line 507-508 for getTargetAdminDelayChangeCall).

Tip

📝 Customizable high-level summaries are now available in beta!

You can now customize how CodeRabbit generates the high-level summary in your pull requests — including its content, structure, tone, and formatting.

• Provide your own instructions using the high_level_summary_instructions setting.
• Format the summary however you like (bullet lists, tables, multi-section layouts, contributor stats, etc.).
• Use high_level_summary_in_walkthrough to move the summary from the description to the walkthrough section.

Example instruction:

"Divide the high-level summary into five sections:

1. 📝 Description — Summarize the main change in 50–60 words, explaining what was done.
2. 📓 References — List relevant issues, discussions, documentation, or related PRs.
3. 📦 Dependencies & Requirements — Mention any new/updated dependencies, environment variable changes, or configuration updates.
4. 📊 Contributor Summary — Include a Markdown table showing contributions:
   | Contributor | Lines Added | Lines Removed | Files Changed |
5. ✔️ Additional Notes — Add any extra reviewer context.
   Keep each section concise (under 200 words) and use bullet or numbered lists for clarity."

Note: This feature is currently in beta for Pro-tier users, and pricing will be announced later.

---

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