Bugfix - allow collections to be burnt #51
+83
−3
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Currently collections cannot be burned due to the burn lifecycle event on a collection not adding any approval * added new burn_self lifecycle event * fail if not update authority * fail if current size != 0 - this would result in an inconsistent state
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
|
noticed this issue as well, would be great to have this supported |
|
We are still discussing this item internally. Thank you for your patience and thank you for the contribution! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Currently collections cannot be burned due to the burn lifecycle event on a collection not adding any approval