feat: add tiered ticket bundle pricing,and configure project-wide edi…#542
Merged
Conversation
This file contains hidden or 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
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.
…tor settings.
Description
In this session, we implemented optional ticket bundle pricing tiers to allow volume discounts during purchases and ensured the effective price is accurately recorded in the
TicketPurchasedevent. To improve code maintainability, we eliminated duplicate authentication logic by extractingrequire_adminandrequire_not_pausedinto shared macros within theraffle-sharedcrate, applying them consistently across both the factory and instance contracts. Additionally, we standardized whitespace and formatting across different IDEs by introducing a repository-wide.editorconfigthat aligns with the existingrustfmt.tomlrules, and we documented this requirement in the setup section of theREADME.md. Finally, we expanded the test suite for the factory contract to comprehensively verify the 48-hour timelock mechanism, guaranteeing that configuration changes correctly fail if executed too early, succeed and persist state updates after the delay, and can be cleanly cancelled.Closes #486
Closes #472
Closes #481
Closes #452
Type of Change
Testing
Contract Changes
Changelog
Security