fix: first_invoice_offset type #83
Merged
Conversation
This file contains 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
|
We will analyze the proposed solution and soon integrate it into our product. |
renanneri01
requested changes
Jan 15, 2025
renanneri01
approved these changes
Jan 15, 2025
|
@OtavioPontes We have already made available a new version (v1.0.9) of the SDK with the property correction. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
In the preapproval package, when trying to unmarshal the Response struct, it throws the error:
"encoding/json.UnmarshalTypeError {Value: "number", Type: reflect.Type(*reflect.rtype) *{t: (*"internal/abi.Type")(0x1eef160)}, Offset: 1243, Struct: "Response", Field: "first_invoice_offset"}".This is because the FirstInvoiceOffset field is of type string, when it should be a integer.