Add api_key to schema
#142
Open
Conversation
This file contains 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
I noticed when editing my prompty file in VS Code that it displayed a yellow squiggly line under `api_key` because it wasn't in the schema. However, the extension is using the field, because executing my prompty fails without it and succeeds with it. I added it to the schema so it's documented and the squiggly line goes away.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
I noticed when editing my prompty file in VS Code that it displayed a yellow squiggly line under
api_keybecause it wasn't in the schema.However, both the extension and the
promptyCLI in the Python runtime are using the field, because, for both, executing my prompty fails without it and succeeds with it.I added it to the schema so it's documented and the squiggly line goes away.