fix: devenv token verifier config should be scoped per family - #1382
fix: devenv token verifier config should be scoped per family#1382huangzhen1997 wants to merge 2 commits into
Conversation
|
👋 huangzhen1997, 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! |
There was a problem hiding this comment.
Pull request overview
This PR updates the devenv token-verifier configuration generation so it targets only the configured chain_family (defaulting to EVM), instead of scanning all chain selectors indiscriminately.
Changes:
- Filter
ChainSelectorspassed intoGenerateTokenVerifierConfigbyTokenVerifierInput.ChainFamily. - Set
ReplaceExisting: truewhen saving generated token-verifier config. - Add a local
filterSelectorsByFamilyhelper in both the monolith and phased-component paths.
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated 2 comments.
| File | Description |
|---|---|
| build/devenv/environment_monolith.go | Filter selectors by ChainFamily before generating token-verifier config; add helper. |
| build/devenv/components/tokenverifier/component.go | Apply the same family-based filtering in the phased tokenverifier component; add helper. |
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
91e40d1 to
97dfc2e
Compare
|
Code coverage report:
|
| ServiceIdentifier: "TokenVerifier", | ||
| ChainSelectors: selectors, | ||
| ChainSelectors: familySelectors, | ||
| ReplaceExisting: true, |
| ServiceIdentifier: "TokenVerifier", | ||
| ChainSelectors: selectors, | ||
| ChainSelectors: familySelectors, | ||
| ReplaceExisting: true, |
No description provided.