We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
If you have a parameter in a message called funds it collides with the funds that one can provide for the coins in the message.
funds
Example:
pub enum AutocompounderExecuteMsg { ... /// Join vault by depositing one or more funds Deposit { funds: Vec<OfferAsset> }, }
export interface AutocompounderInterface extends AutocompounderReadOnlyInterface { ... deposit: ( { funds, }: { funds: AnsAsset[] }, fee?: number | StdFee | 'auto', memo?: string, funds?: Coin[] ) => Promise<ExecuteResult> ... }
I propose that we rename fee, memo, and funds to their underscored variants: _fee, _memo, and _funds.
fee
memo
_fee
_memo
_funds
The text was updated successfully, but these errors were encountered:
oh interesting! totally good idea
we can put it under a flag called underscoreMetaParams or something that makes sense
underscoreMetaParams
Sorry, something went wrong.
No branches or pull requests
If you have a parameter in a message called
funds
it collides with thefunds
that one can provide for the coins in the message.Example:
I propose that we rename
fee
,memo
, andfunds
to their underscored variants:_fee
,_memo
, and_funds
.The text was updated successfully, but these errors were encountered: