Feat: REST ticket type management and event creation#53
Open
tarynblakemiller wants to merge 10 commits intomainfrom
Open
Feat: REST ticket type management and event creation#53tarynblakemiller wants to merge 10 commits intomainfrom
tarynblakemiller wants to merge 10 commits intomainfrom
Conversation
c344fed to
43d6a88
Compare
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.
This PR has admittedly expanded as I arrived at event creation!!
I should note that I pulled in Jack's DB models branch in order to finish this.
Description
Type of Change
Changes Implemented
CRUD operations for ticket types
GET /tickets - List all ticket types
GET /tickets/new - Creation form
POST /tickets/new - Create ticket
GET /tickets/{id} - View ticket (read-only)
GET /tickets/{id}/edit - Edit form
POST /tickets/{id}/edit - Update ticket
POST /tickets/{id}/delete - Delete ticket
Events can now be created with a ticket type and flyer image
GET /events - List events with cover image thumbnails
GET /events/new - Creation form with ticket selection
POST /events/new - Create event with tickets and image
GET /events/{id} - View event (read-only with ticket details)
GET /events/{id}/edit - Edit form
POST /events/{id}/edit - Update event
POST /events/{id}/delete - Delete event
##Image Processing
**this was just a placeholder please feel free to critique and change!
I added an image processing module to the templates and a temporary storage path for images.
This added base64 and uuid dependencies.
Storage path: frontend/static/uploads/images/events/
Web path: /static/uploads/images/events/
Testing
Ticket Types
Event Creation