You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Recommends to run/use cargo clippy + cargo +nightly fmt in an automated CI/CD (github actions). Working on it
Recommend creating some integration tests using zombienet. Since Ternoa is not having parachain setup yet this stands invalid. But it's in our roadmap
Use a const to refer to big numbers (Balance amounts): DONE! Here is the [PR](https://github.com/capsule-corp-ternoa/ternoa-node/pull/306) for it.
Usage of a global NFT/Collection/Marketplace id as a counter (u32, ~4.3B) can be handy for some logic but not that flexible. We don't see an exact usecase for it as of now. Please let us know an instance where this could be useful.
Using StorageDoubleMap with {(collectionId, nftId) -> data} could be interesting. Or even a "triple" StorageMap, like pallet-nfts does here:
That way users would be able to "mint" more than one NftId: 1. As each Collection would have its own first NFT (1). But in our case we have separate collection data as well which we are handling in Collections storage map. and in the NFTData we are mapping the collection_id to it like below. Even now users would be able to mint more than one Nft.
Recommends moving all ensure!(nft, ...) duplicated blocks (checks) to a generic function, customized for each case. This could be done if there are many duplicated checks with same errors in multiple extrinsics. But most of the error we have defined are specific to each extrinsic even though some checks are duplicated.
ensure_root() could be replaced by a more democratic Origin (like a Council) . This is our end goal but right now we are good with _ensure_root()_
Calling an extrinsic from another is not a good practice. We'd recommend creating a simple Pallet function for that. DONE! Here is the [PR](https://github.com/capsule-corp-ternoa/ternoa-pallets/pull/72) for it.
The text was updated successfully, but these errors were encountered:
Working on it
Since Ternoa is not having parachain setup yet this stands invalid. But it's in our roadmap
DONE! Here is the [PR](https://github.com/capsule-corp-ternoa/ternoa-node/pull/306) for it.
We don't see an exact usecase for it as of now. Please let us know an instance where this could be useful.
That way users would be able to "mint" more than one NftId: 1. As each Collection would have its own first NFT (1).
But in our case we have separate collection data as well which we are handling in Collections storage map. and in the NFTData we are mapping the collection_id to it like below. Even now users would be able to mint more than one Nft.
This could be done if there are many duplicated checks with same errors in multiple extrinsics. But most of the error we have defined are specific to each extrinsic even though some checks are duplicated.
This is our end goal but right now we are good with _ensure_root()_
DONE! Here is the [PR](https://github.com/capsule-corp-ternoa/ternoa-pallets/pull/72) for it.
The text was updated successfully, but these errors were encountered: