feat: serve the spec as JSON#323
Merged
Merged
Conversation
The spec dict is already parsed at registration time, so serving it as JSON is just another view on the same data. Off by default. Resolves Pylons#10
miketheman
force-pushed
the
feat/10-serve-json-spec
branch
from
63e5047 to
c22e325
Compare
Collaborator
|
Is there a cost to serving JSON? What if we serve it by default and reduce some code complexity? |
json.dumps on an already-parsed dict is free, and the earlier opt-in flag mostly added branching rather than avoiding real cost. The JSON route path is derived from route (extension swapped to .json) so multi-spec apps with different apinames don't collide.
Collaborator
Author
|
Fair question, I figured it wasn't there before, so this could be opt-in. I pushed a second commit with serving json by default - let me know what you think of that approach if it's simpler/cleaner. |
miketheman
changed the title
zupo
approved these changes
Jul 4, 2026
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
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.
The spec dict is already parsed at registration time, so serving it as JSON is just another view on the same data.
Off by default.Resolves #10