-
Notifications
You must be signed in to change notification settings - Fork 13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: HTTP Generator #32
Conversation
Deploying rigging-docs with Cloudflare Pages
|
|
||
# Spec types | ||
|
||
InputTransform = t.Literal["json", "jinja"] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
should the input also include jsonpath
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think of jsonpath
as being an extractor mechanism (removing information), and json
as formatting (adding information).
Def open to some example use cases though, lots of options for blending.
Example use:
Generated Summary
jsonpath-ng
andruamel-yaml
inpyproject.toml
.HTTPGenerator
for mapping messages to HTTP requests and responses inrigging/generator/http.py
.HTTPSpec
, including transformation mechanisms for both inputs and outputs.ProcessingError
to manage exceptions during processing.HTTPSpec
, covering key functionalities including request creation, response parsing, and error scenarios.__init__.py
to include the newHTTPGenerator
and modified imports to include thegenerator
.This summary was generated with ❤️ by rigging