added transferTicketOwnership, refundTicket and searchEvents #1
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.
This PR introduces three additional advanced functions to enhance this canister'sfunctionality.
Transfer Ticket Ownership
The
transferTicketOwnershipfunction allows users to transfer ownership of a ticket from one user to another. It takes the following parameters:ticketId: The ID of the ticket to be transferred.currentHolderId: The ID of the current ticket holder.newHolderId: The ID of the new ticket holder.password: The password of the current ticket holder for authentication.Example usage:
Refund Ticket
The refundTicket function allows ticket holders to request a refund for their ticket. It takes the following parameters:
ticketId:The ID of the ticket to be refunded.password: The password of the ticket holder for authentication.Example usage:
Event Search
The searchEvents function enables users to search for events based on various criteria. It takes the following parameters (all optional):
eventName: The name of the event.organizer: The organizer of the event.date: The date of the event.location: The location of the event.Example usage:
Please refer to the function descriptions and examples above for a high-level understanding of their usage within the Ticket Management System.