Added waitingListOpen boolean to event type

[AndrewBestbier]

Motivation

After a discussion with Amy, Tania and Sammy it was decided that a new 'switch' will be needed on the prismic site to enable the entire ticket release process. This boolean is 'waitingListOpen'.

The current process is then:

Step 1

• Amy adds Event Start Time
• Amy adds Event End Time
• Amy adds Ticket Release Time
• Amy sets tickets available to False.
• Amy sets the event link to an empty string.
• Amy sets the streaming link to an empty string.
• Amy sets waiting list open to False.
• The current time is before the Ticket Release Time.

Step 2

• Amy sets tickets available to True.
• Amy sets the event link to the relevant site (EventBrite/Facebook etc).
• The current time is after the Ticket Release Time.

Step 3

• Amy sets tickets available to False.
• Amy sets waiting list open to True

Step 4

• Amy sets waiting list open to False

Step 5

• Amy sets the streaming link to the relevant youtube link

Step 6

• The current time is after the event end time

Thoughts

This may be relatively tricky to program bearing in mind that Prismic does not allow us to have mandatory fields. Another suggestion would be to edit all the fields manually.

For example, in Prismic, the user could edit the button text, button link, event status title etc. However, this would result in a process that requires much more manual work.

[asavin]

I suppose this is when we could implement the validation layer in Badger Brain, as proposed in #43

It doesn't look easy, but considering that we only have 1 admin user, should be alright. Basically - set values into fields, check on live site.

[lpil]

Wouldn't it make more sense to have a 3 value enumeration over a boolean? This section has multiple states- it's hard to represent this with boolean values, and results in awkward and complex logic trees like the one detailed in the post.