V2 event rework #126
Merged
V2 event rework #126
Conversation
This file contains 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
…must manually invite or set to attend
…ons, big cleanup of sms messages
… user relative to the id of the event. horror.
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 is the big one.
Adding in the idea of a "Session".
It's single user, multi-person. We can send invitations, reminders, people can cancel and confirm via sms, etc.
Essentially, it rips up the whole "V2::" system and replaces it with a smaller footprint, largely because it leaves the scheduling to the users and the people, and then manages the reminding and notifications to the app.
It's largely test free at the moment, which will need to change, but not untill this sprint is done, I'm afraid.