-
Notifications
You must be signed in to change notification settings - Fork 209
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
fix(api-kit): Missing to
parameter
#1058
Conversation
Pull Request Test Coverage Report for Build 12008535981Details
💛 - Coveralls |
return sendRequest({ | ||
url: `${this.#txServiceBaseUrl}/v1/data-decoder/`, | ||
method: HttpMethod.Post, | ||
body: { data } | ||
body: dataDecoderRequest |
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.
Can we simplify this to?:
body: to ? { to, data } : { data }
* @returns The transaction data decoded | ||
* @throws "Invalid data" | ||
* @throws "Not Found" | ||
* @throws "Ensure this field has at least 1 hexadecimal chars (not counting 0x)." | ||
*/ | ||
async decodeData(data: string): Promise<any> { | ||
async decodeData(data: string, to?: string): Promise<any> { |
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.
Can use this Type instead of Promise<any>
?
type DecodeParameterType = {
name: string
type: string
value: string
}
type DecodeReturnType = {
method: string
parameters: DecodeParameterType[]
}
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.
I don't see the correct type on the service:
https://safe-transaction-sepolia.staging.5afe.dev/#/data-decoder/data_decoder_create
https://github.com/safe-global/safe-transaction-service/blob/f446d55cb527358e5312cea5aa737e0bae1adc6c/safe_transaction_service/history/views.py#L1188-L1225
The return type i'm seeing does not match the { data, to } structure that is in reality the parameters. So not sure if that type is always going to be the one or it can change
What it solves
Resolves #1046
How this PR fixes it
Adding the
to
parameter to thedecodeData
method