fix: Bug in pdl_schema_error_analyzer that raises exception during analysis #851
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
When the PDL doesn't match the schema, the error analysis fails as it attempts to retrieve the field names without verifying that
"properties"
key exists inref_type
.This change returns an empty
dict
ifproperties
key doesn't exist inref_type
to allow the error analysis to complete successfully.Fixes: #850
Sample PDL
Expected Error
Actual Error
NOTE: I attempted to run
pytest tests
andpre-commit run --all-files
, but they fail since I don't have the granite models. The same tests fails without my changes as well.