-
Notifications
You must be signed in to change notification settings - Fork 28
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
Check the NFT data for nil when updating the dynamic data. #813
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #813 +/- ##
==========================================
+ Coverage 35.58% 36.82% +1.23%
==========================================
Files 165 165
Lines 48956 48959 +3
==========================================
+ Hits 17420 18027 +607
+ Misses 28149 27529 -620
- Partials 3387 3403 +16
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
deef7a7
to
08eead3
Compare
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.
Reviewed 2 of 2 files at r1, all commit messages.
Reviewable status: all files reviewed, 1 unresolved discussion (waiting on @dzmitryhil, @masihyeganeh, @miladz68, and @wojtek-coreum)
x/asset/nft/keeper/keeper.go
line 382 at r1 (raw file):
return sdkerrors.Wrapf(types.ErrNFTNotFound, "nft with classID:%s and ID:%s not found", classID, id) } if storedNFT.Data == nil {
btw do we have check that our Data changes are compatible with v3 ?
Maybe we need to add test into upgrade integration tests ?
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.
Reviewable status: all files reviewed, 1 unresolved discussion (waiting on @masihyeganeh, @miladz68, @wojtek-coreum, and @ysv)
x/asset/nft/keeper/keeper.go
line 382 at r1 (raw file):
Previously, ysv (Yaroslav Savchuk) wrote…
btw do we have check that our Data changes are compatible with v3 ?
Maybe we need to add test into upgrade integration tests ?
We didn't change the data, so it's compatible.
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.
Reviewed 2 of 2 files at r1, all commit messages.
Reviewable status: all files reviewed, 1 unresolved discussion (waiting on @masihyeganeh, @wojtek-coreum, and @ysv)
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.
Reviewable status: complete! all files reviewed, all discussions resolved (waiting on @masihyeganeh and @wojtek-coreum)
Description
Check the NFT data for nil when updating the dynamic data.
Reviewers checklist:
Authors checklist
This change is