Separated NFT grid #195
Separated NFT grid #195
Conversation
* PageNumber with two-way binding because it's a query parameter of the contained page * own OnParametersSetAsync with typical CTS logic * implements IDispose so it can cancel possibly running OnParameter... * collections page now keeps a maxPageCount so you don't loose that info if you're going back pages
* needed for chip with balance * collection page transforms list of NonFungibleToken to list of AccountNFTSlots, only setting nft field * now variables like NFTSlots are no longer misleading, because they are slots (again) * only show chip with balance if it's positive
* now that we're only loading the slots and the actual NFTs are loaded asynchronously in NFTGrid, it's better to load them before transactions, because a) these take long to load and b) they're displayed last so should be loaded last
|
We should wait with merging this into production! I've just found out that, because the NFTGrid is now a child component, it's That is problematic, because every new call to |
|
Ahhhh I didn't notice that in the console. Thanks for the heads up then. |
Closes #193
Wow, that has been quite a ride, lots of new things learnt, but I think I got everything! Cancellation etc. work, directly changing page numbers via the URL etc. all still seem to work just fine!
No visual changes AFAICS.
The grid needs to have a list of
AccountNFTSlot, notNonFungibleToken, for it to display the balance - when viewing on AccountDetails. For the collection view, a LINQ transformation of the list is therefore necessary, but I don't think that'll hurt.Please give it a thorough test drive on dev.
Now that this is separated out, we can tackle #180