-
Notifications
You must be signed in to change notification settings - Fork 18
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
add multi-owner cw-ownable
with cosmwasm v2
#25
Conversation
…singleton. But can be re-use e.g. by defining `CREATOR: OwnershipStore = OwnershipStore::new("creator")`
* move all logic to `OwnershipStore`. This way `cw-ownable` is still a singleton. But can be re-use e.g. by defining `CREATOR: OwnershipStore = OwnershipStore::new("creator")` * cargo fmt * cargo clippy --tests * use api and storage (instead of DepsMut) for being less restrictive * fix ownable * remove unneccessary lifetime (clippy warning) --------- Co-authored-by: mr-t <[email protected]>
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.
I think it makes sense to expose the OwnershipStore
object but we should aim to keep the remaining API the same, following the cw2 ways of doing things.
That all makes sense to me. I'm not too familiar with the context and overall architecture of this whole thing; my main goal here is to enable the cw-nfts cosmwasm v2 upgrade (public-awesome/cw-nfts#172) and I don't expect any of those edits would be an issue for it, maybe some minor changes. |
* update ownable exports and revert API breaking change * fully revert update_ownership breaking API change and fix relevant tests
Thanks for contributing! I exported the Item's key so you can still construct the |
Includes work by @taitruong from #21
cw-ownable
(Multiple ownership public-awesome/cw-plus-plus#1)cw-ownable
for CosmWasm v2 compatibilityUnblocks public-awesome/cw-nfts#160 and indirectly DA0-DA0/dao-contracts#840