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.
This PR contains a first draft for setting up Guard as a Runnable for use within LCEL.
It is based on the first draft of chaining.
The Guard wrapper presented here is captured in a different class that inherits from our (not really) functional/chaining Guard so we can decide if we want this to exist in this repo or as a separate package. The downside of including it here is it increases our dependency size since it requires langchain_core
This PR also includes a refactor of the
ValidatorError
class toValidationError
. The reasons for this refactor are in the comments inguardrails/errors/__init__.py
. The reason this refactor is included in this PR is because we are usingValidationError
to raise frominvoke
in the event that the input fails validation. We raise to prevent parsing errors since failed validation means an output of None. If we want to take a different approach the more specific commits of this PR can be picked onto a new branch; just lmk via review.Try it out: