-
Notifications
You must be signed in to change notification settings - Fork 25
feat(vault-v1&2): add factory check in fetch utilities #504
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
feat(vault-v1&2): add factory check in fetch utilities #504
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: c1b6f004ab
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: c426f643dd
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
packages/blue-sdk-viem/src/fetch/vault-v2/VaultV2MorphoMarketV1Adapter.ts
Show resolved
Hide resolved
…in fetchVault function
…andling and code formatting
| import {IMorphoMarketV1AdapterV2Factory} from "./interfaces/IMorphoMarketV1AdapterV2Factory.sol"; | ||
| import {IVaultV2Factory} from "./interfaces/IVaultV2Factory.sol"; | ||
|
|
||
| error UnknownFromFactory(address factory, address vault); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| error UnknownFromFactory(address factory, address vault); | |
| error UnknownOfFactory(address factory, address vault); |
no?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What did I do?
What’s your proposal?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just the naming "unknown of" seems more appropriate than "unknown from"!
But actually, it may even be better to say "unknwon to": https://chatgpt.com/share/e/697b0e61-edd0-8004-a49d-8f965d6d62df
| error UnknownFromFactory(address factory, address vault); | |
| error UnknownToFactory(address factory, address vault); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Mmm i prefer UnknownOfFactory:
Because it means the object is valid but does not belong to this factory (it was created by another one or the ownership link is incorrect).
And UnknownToFactory is not the destination of the call (the factory is correct), but the ownership relationship between the object and that factory.
…vaults-in-sdk-fetchers-v1-and-2
Uh oh!
There was an error while loading. Please reload this page.