Implement event publishing

lebull commented 1 month ago

This is what I had in mind for event publishing.

There are two separate endpoints now for both getting the lineup text, and getting the lineup for the ObsConfigGenerator. The latter will get the next event, even if it's not published. The lineup text will only get the next published event.
I think this should be a very visible part of the process instead of nested in one of our tabs. I added a badge to the top of the event root, and if the event is not published, I added a button to publish it.
- The user is prompted to save changes if there are any unsaved changes and they try to publish
In case we need to "unpublish" an event, there is a toggle on the event basic setup form. This behaves like all the other form inputs.

github-actions[bot] commented 1 month ago

Visit the preview URL for this PR (updated for commit e9f2aeb):

_{(expires Wed, 14 Aug 2024 00:13:09 GMT)}

_{Sign: 58385af7bd5a89154351e3a6f5764ea3ef89db5c}

lebull commented 1 month ago

Toasts are in

SundayServiceVR / sunday-service-vr