Repository navigation
Conversation
|
👋 SyedAsadKazmi, thanks for creating this pull request! To help reviewers, please consider creating future PRs as drafts first. This allows you to self-review and make any final changes before notifying the team. Once you're ready, you can mark it as "Ready for review" to request feedback. Thanks! |
aelmanaa
approved these changes
Sep 23, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fix docs lint + rotting fork-test onRamp constant
Docs lint:
README.md:162used an em-dash (—), whichnpm run docs:checkrejects. Replaced with a spaced hyphen (-). Check now passes clean across all 121 files.Fork tests: 6 tests in
test/reference/RateLimiterVersionBehavior.t.solfailed withCallerIsNotARampOnRouterbecauseV200_ONRAMPwas a hardcoded constant that rotted when Sepolia's router config drifted - the Fuji lane's onRamp moved to a new address. Replaced the constant with a dynamic resolution insetUp: read the pool's current router viagetDynamicConfig(), then resolve the lane's onRamp viarouter.getOnRamp(FUJI). The tests now track live router state instead of breaking on the next ramp migration.