dlt-hub / dlt-hub/dlt-init-openapi
Render LLM Helpers
- Dominant language
- Python
- Stars
- 39
- Forks
- 8
- PR merge metrics
- No merged PRs in 30d
Description
We could could also output some additional info the user can use for prompting, example:
When rendering endpoints, let's dump useful LLM information into a text file that may be used for prompting (manual).
Ideally for each rendered endpoints we have a path fragment of openAPI spec that contains the following
only GET operation
parameters but dereferenced
actual response that we picked
in the response the schema should be de-referenced (but maybe only to the 2 nesting level)
examples should be kept
let's render using yaml. this is what LLM will understand
if we detected parent endpoint let's give path to it.
Contributor guide
Research direction
Start by locating the endpoint-rendering entry point and the code that reads and dereferences the OpenAPI document. The work is done when each rendered endpoint produces a YAML file containing the requested GET operation details, parameters, selected response, limited schema dereferencing, examples, and any parent-endpoint path.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- api, backend-api-design
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 28/100