Fix marketing copy structured output schema#156
Open
stuartmac wants to merge 1 commit intodocker:mainfrom
Open
Fix marketing copy structured output schema#156stuartmac wants to merge 1 commit intodocker:mainfrom
stuartmac wants to merge 1 commit intodocker:mainfrom
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Summary
Fixed an output validation issue in the CrewAI marketing posts example.
When running the example, the pipeline consistently failed on the final step with the
Creative Content Creatoragent and raised a PydanticValidationError.The final task generates multiple pieces of marketing copy, but the configured output schema only accepts a single
Copyobject.Fix
Added a
Copieswrapper model and updatedcopy_creation_taskto use that schema instead, so the final output can include a list of copy text items.The pipeline consistently completes, and I have not seen the validation error again.