Unify Calendar and Event sections [SA-19565] (master) #170
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 removes the errant
Eventsection.These sections are grouped by the
tagsnode, so havingtags: [calendar, event]creates two sections - one called Calendar and another called Event - with the exact same contents in each. I'm not sure why someone would try to intentionally dupe those in this manner.Anyway, I've combined them into the Calendar section. The maintenance of calendar events and the invitations to/attendances thereof, are (to me) still logically classified under Calendar.
If you wanted event attendance specifically in its own section, you could still do that: but you have to make sure that only the attendance yamls use the
eventtag, not just proliferate it everywhere blindly.imho I think you'd want all your calendar event management stuff in one place, not separated like this at one end of the api docs and also at the other. How annoying is that