events: document follow/follow_state/followers/comments in swagger#776
Merged
dylanjeffers merged 1 commit intomainfrom Apr 22, 2026
Merged
events: document follow/follow_state/followers/comments in swagger#776dylanjeffers merged 1 commit intomainfrom
dylanjeffers merged 1 commit intomainfrom
Conversation
These handlers existed on the Go side already (v1EventFollowState,
postV1EventFollow, deleteV1EventFollow, v1EventComments, plus the new
v1EventsFollowers) but never got entries in the hand-maintained
swagger-v1.yaml. As a result the SDK generator — which reads that YAML
— produced no TS types for them, and every consumer had to either
hand-stub the types or route through the entity-manager escape hatch.
Adds paths for:
- GET /events/{eventId}/comments → track_comments_response
- POST /events/{eventId}/follow → write_response (auth required)
- DELETE /events/{eventId}/follow → write_response (auth required)
- GET /events/{eventId}/follow_state → event_follow_state_response
- GET /events/{eventId}/follow-state → event_follow_state_response
(hyphenated alias)
- GET /events/{eventId}/followers → followers_response
Adds event_follow_state / event_follow_state_response schemas. Other
endpoints reuse existing track_comments_response / write_response /
followers_response shapes since the response envelopes are identical.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
These handlers existed on the Go side already (v1EventFollowState, postV1EventFollow, deleteV1EventFollow, v1EventComments, plus the new v1EventsFollowers) but never got entries in the hand-maintained swagger-v1.yaml. As a result the SDK generator — which reads that YAML — produced no TS types for them, and every consumer had to either hand-stub the types or route through the entity-manager escape hatch.
Adds paths for:
(hyphenated alias)
Adds event_follow_state / event_follow_state_response schemas. Other endpoints reuse existing track_comments_response / write_response / followers_response shapes since the response envelopes are identical.