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.

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(template): added no-legacy-stdTx flag #130

Merged
merged 1 commit into from
Nov 23, 2021

Conversation

marinhoarthur
Copy link
Contributor

@marinhoarthur marinhoarthur commented Nov 19, 2021

@fadeev
Copy link
Contributor

fadeev commented Nov 19, 2021

@marinhoarthur does this PR fixes #128?

@marinhoarthur
Copy link
Contributor Author

@fadeev yes

@fadeev fadeev changed the title added no-legacy-stdTx flag fix(keplr): added no-legacy-stdTx flag Nov 19, 2021
@fadeev fadeev changed the title fix(keplr): added no-legacy-stdTx flag fix(template): added no-legacy-stdTx flag Nov 19, 2021
Copy link
Contributor

@Matthews3301 Matthews3301 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Verified, this solves the problem.

Copy link
Contributor

@mihailmarcu mihailmarcu left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hey @marinhoarthur,
After our session where we reproduced the issue and tested the final fix I can tell that your solution fixed this error.

You can easily go and merge the changes.

Checklist when testing a PR

  • Code review
  • The bug was reproduced locally
  • Manual testing performed
  • Changes made fixed the bug
  • No potential merge conflicts with develop

@marinhoarthur marinhoarthur merged commit 01a05ee into develop Nov 23, 2021
@marinhoarthur marinhoarthur deleted the feature/keplr-no-legacy-flag branch November 23, 2021 18:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants