Skip to content

Conversation

@stevechan
Copy link
Contributor

This removes the errant Event section.

image

These sections are grouped by the tags node, so having tags: [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 event tag, not just proliferate it everywhere blindly.

calendar@event@attendance@{id}.yaml

get:
  operationId: getCalendarEventAttendance
  tags: [event]

image

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

@stevechan stevechan changed the base branch from develop to master April 30, 2025 05:22
@JustinAClarke JustinAClarke merged commit 66f218d into alaress:master May 5, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants