-
Notifications
You must be signed in to change notification settings - Fork 11.3k
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
[framework] don't emit event on purchase with PurchaseCap #12821
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎ 6 Ignored Deployments
|
@damirka, we're trying out an extra step in the release process for user facing changes, where we ping @randall-Mysten / @ronny-mysten on the docs channel to review the release notes before the change lands as well -- could you do that before landing please? Change looks good! |
I updated the Release notes section. Let me know if something doesn't make sense. |
8504574
to
2bef4a8
Compare
## Motivation PurchaseCap functionality is created specifically for extensions and logic which may or may not be considered trading. And emitting an event when "purchasing" with the Cap breaks indexers and makes little sense - ItemListed is not emitted, ItemDelisted as well. Currently, all extensions rely on custom events for this purpose. ## Description Changes the body of the `kiosk::purchase_with_cap` to NOT emit the ItemPurchased event. Everything else is left intact. ## Test Plan Current tests pass. ### Type of Change (Check all that apply) - [ ] protocol change - [x] user-visible impact - [ ] breaking change for a client SDKs - [ ] breaking change for FNs (FN binary must upgrade) - [ ] breaking change for validators or node operators (must upgrade binaries) - [ ] breaking change for on-chain data layout - [ ] necessitate either a data wipe or data migration ### Release notes - The `kiosk::purchase_with_cap` method for [Sui Kiosk](https://docs.sui.io/build/sui-kiosk) no longer emits the `ItemPurchased` event. This is a network optimization update that should have minimal impact. If the logic of your application does rely on this event, you must change it to leverage custom events instead.
## Motivation PurchaseCap functionality is created specifically for extensions and logic which may or may not be considered trading. And emitting an event when "purchasing" with the Cap breaks indexers and makes little sense - ItemListed is not emitted, ItemDelisted as well. Currently, all extensions rely on custom events for this purpose. ## Description Changes the body of the `kiosk::purchase_with_cap` to NOT emit the ItemPurchased event. Everything else is left intact. ## Test Plan Current tests pass. ### Type of Change (Check all that apply) - [ ] protocol change - [x] user-visible impact - [ ] breaking change for a client SDKs - [ ] breaking change for FNs (FN binary must upgrade) - [ ] breaking change for validators or node operators (must upgrade binaries) - [ ] breaking change for on-chain data layout - [ ] necessitate either a data wipe or data migration ### Release notes - The `kiosk::purchase_with_cap` method for [Sui Kiosk](https://docs.sui.io/build/sui-kiosk) no longer emits the `ItemPurchased` event. This is a network optimization update that should have minimal impact. If the logic of your application does rely on this event, you must change it to leverage custom events instead.
Motivation
PurchaseCap functionality is created specifically for extensions and logic which may or may not be considered trading. And emitting an event when "purchasing" with the Cap breaks indexers and makes little sense - ItemListed is not emitted, ItemDelisted as well.
Currently, all extensions rely on custom events for this purpose.
Description
Changes the body of the
kiosk::purchase_with_cap
to NOT emit the ItemPurchased event. Everything else is left intact.Test Plan
Current tests pass.
Type of Change (Check all that apply)
Release notes
kiosk::purchase_with_cap
method for Sui Kiosk no longer emits theItemPurchased
event. This is a network optimization update that should have minimal impact. If the logic of your application does rely on this event, you must change it to leverage custom events instead.