Ticket List #53
Description
a. This page should be like any other list page, on the row click the Update action happens.
b. Do not show the PricingTiers like this, it should be a component on the Update Page like any other model object. The component for PricingTiers type will allow a ticket to be selected from a select tool, much like how we select an image or several images. The items that are allowed in here are items that exist Store.Items. This contains all of the “tickets” available for a store so this is where your lookup data comes from. All items in a store exists in Store.Items, however a ticket only belongs to an event when it is also added to Event.Items or is connected via PricingTiers. Being able to create a new ticket quickly from the PricingTiers tool would be handy, much like the image upload in the Media Library allows adding new images.
c. The Ticket List itself should be a component in the Event Update Page. It should be treated as its own component as it can exist outside of an event (example, the PricingTiers create function).
d. Several of the Sales Dates are showing NAN, because DateOnly, DateTime and TimeOnly are the three types for a DateTime type, the control to edit and display these types should make sure that empty values are handled correctly application wide. On the display, show nothing, in the edit the default can be now if not other default has been defined already.
