Update Ailly response parser to expect a different format #168
Conversation
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
cpyle0819
force-pushed
the
corepyle/iam-format-change
branch
from
91ea448 to
d705845
Compare
Change the parsers expected format to be something less complex than JSON. Also add example policy prefixes.
cpyle0819
force-pushed
the
corepyle/iam-format-change
branch
from
ee35033 to
730c9a2
Compare
DavidSouther
approved these changes
May 20, 2025
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.
Previously, we were asking the LLM to output JSON. This proved difficult to parse as it frequently gave invalid formatting. This change expects the output to be a new, custom, format.
This also adds prefixes to
titleandtitle_abbrevvalues.By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.