fix: make resources field optional with empty default in AgentDefinition #1047
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
resourcesfield optional inAgentDefinitionby addingdefault_factory=listProblem
The
resourcesfield inAgentDefinitionwas defined as a required field without a default value:This caused validation errors when loading
agent.jsonfiles that don't include aresourcesarray:Root Cause
In commit
7016737("fix: agent resources discriminator"), theAgentDefinitionmodel was refactored from separateLowCodeAgentDefinitionandCodedAgentDefinitionclasses into a unified model. During this refactor, theresourcesfield was made required without a default value.Solution
Add
default_factory=listto theresourcesfield, matching the pattern already used byfeatures:Impact
This fix restores backward compatibility for:
agent.jsonfiles created before resources were addedTest plan
resourcesfield load successfullyresourcesfield still work correctly🤖 Generated with Claude Code