fix: correct comment typo in getAccessChangeCall rule

[hawkadrian]

The comment said "values before" but should be "values after" since it appears after the function call.

[changeset-bot]

⚠️ No Changeset found

Latest commit: 0bc1835

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 AccessManager specification file was updated from "values before" to "values after" in the getAccessChangeCall section. No functional logic, control flow, or exported entity declarations were modified in this change.

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately describes the main change: correcting a comment typo in the getAccessChangeCall rule from 'values before' to 'values after'.
Description check	✅ Passed	The description is directly related to the changeset, clearly explaining the typo correction and the reason for the change.
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 6308fdc and 0bc1835.

📒 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). (9)

• GitHub Check: Redirect rules - solidity-contracts
• GitHub Check: Header rules - solidity-contracts
• GitHub Check: tests-foundry
• GitHub Check: slither
• GitHub Check: tests-upgradeable
• GitHub Check: tests
• GitHub Check: coverage
• GitHub Check: halmos
• GitHub Check: Pages changed - solidity-contracts

🔇 Additional comments (1)

fv/specs/AccessManager.spec (1)

340-340: Accurate comment correction that improves consistency.

The comment update from "values before" to "values after" is correct. Line 340 precedes the retrieval of the "after" values (lines 341–344), and this placement aligns with the established pattern used throughout the file in other similar rules (e.g., getAccessChangeTime, isTargetClosedChangeCall, getTargetFunctionRoleChangeCall).

---

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