You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm working with an internal DSL defined in YAML. The structure is fairly complex, with nested elements, metadata fields, and specific naming conventions.
I'd like to use Codex to help generate this YAML from natural language prompts, but to do this effectively, Codex needs some understanding of the expected schema and format.
I have internal documentation that fully describes the structure and rules of this YAML format. My questions are:
What are the best practices for providing Codex with this kind of context?
Is it better to include examples in the prompt itself, or to fine-tune a model if I need more consistent output?
Are there recommended approaches or tools to help Codex "understand" a schema or DSL without exposing proprietary formats?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
I'm working with an internal DSL defined in YAML. The structure is fairly complex, with nested elements, metadata fields, and specific naming conventions.
I'd like to use Codex to help generate this YAML from natural language prompts, but to do this effectively, Codex needs some understanding of the expected schema and format.
I have internal documentation that fully describes the structure and rules of this YAML format. My questions are:
Beta Was this translation helpful? Give feedback.
All reactions