Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Tx.unpackAny doesn't consider isClassic #317

Closed
tuloski opened this issue Jul 18, 2022 · 2 comments · Fixed by #319
Closed

Tx.unpackAny doesn't consider isClassic #317

tuloski opened this issue Jul 18, 2022 · 2 comments · Fixed by #319

Comments

@tuloski
Copy link

tuloski commented Jul 18, 2022

When using Tx.unpackAny it seems it doesn't consider the isClassic parameter of the LCD.
So for example when unpacking a MsgAggregateExchangeRateVote message with isClassic: true, it trows an error: "Error: Not supported for the network".
@Vritra4
Copy link
Contributor

Vritra4 commented Jul 19, 2022 •
edited
Loading

thanks for your report! it’ll be fixed soon. please wait for the new release.

@Vritra4 Vritra4 mentioned this issue Jul 19, 2022
Merged
@tuloski
Copy link
Author

tuloski commented Jul 20, 2022

Any tip on how to test a specific commit without waiting for a release? Because when installing with npm to a specific commit instead of a tag it doesn't install the "dist" folder and the package can't be used. Any way to bypass this?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

use isClassic flag inside of packAny() and unpackAny() terra-money/terra.js
2 participants
@tuloski @Vritra4