-
Notifications
You must be signed in to change notification settings - Fork 24
allow edits for inactive prizes #242
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
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change | ||||
|---|---|---|---|---|---|---|
|
|
@@ -184,7 +184,7 @@ contract Raffle is Initializable, AccessControlUpgradeable, UUPSUpgradeable { | |||||
| uint256 value, | ||||||
| uint256 quantity, | ||||||
| string calldata formId | ||||||
| ) external onlyRole(ADMIN_ROLE) prizeIsActive(prizeId) { | ||||||
| ) external onlyRole(ADMIN_ROLE) { | ||||||
| // Update prize details without affecting tickets or active status | ||||||
|
||||||
| // Update prize details without affecting tickets or active status | |
| // Update prize details (name, description, value, quantity, formId) for both active and inactive prizes without affecting tickets or the active status |
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.
Removing the
prizeIsActivecheck allows modification of prize details after the prize lifecycle has completed. This could lead to data integrity issues if prize information (name, value, quantity) is changed after winners have been determined, potentially creating inconsistencies in historical records or audit trails. Consider implementing a more granular permission system that allows editing only specific fields likeformIdfor inactive prizes while restricting changes to core prize attributes.