V4/Events: Import Response Examples From Pyro Generated Models #165
+813
−788
Conversation
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
ihassanein
force-pushed
the
iman/add-generated-model-snippet
branch
from
1f8183a to
4790d42
Compare
ihassanein
force-pushed
the
iman/add-generated-model-snippet
branch
from
4790d42 to
96f183c
Compare
ihassanein
force-pushed
the
iman/add-generated-model-snippet
branch
from
96f183c to
d3f4bc1
Compare
Contributor
Author
|
I have made adjustments and now the tabs match in name and in order for field descriptions and response examples 
|
aviau
approved these changes
Feb 4, 2026
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
As there are many different responses possible for this endpoint, and many of them have very drastic differences, we would like one place to import all the response examples. This file is generated via a test in pyro and then copied to event_model_examples.mdx
The resulting page is as shown:
Screen.Recording.2026-02-02.at.1.10.54.PM.mov