fix: handle missing related asset fields in assetsToDf function#231
Merged
fix: handle missing related asset fields in assetsToDf function#231
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
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 pull request improves the robustness of the
assetsToDffunction instixToDf.pyby adding error handling and logging for missing fields in related asset data. This ensures that missing or incomplete data does not cause the export process to fail and provides clear error messages for easier debugging.Error handling and logging improvements:
name,related_asset_sectors, anddescriptionfields in eachrelated_asset. If any of these fields are missing, a detailed error message is logged and a blank value is added to the corresponding output field, allowing the export to continue smoothly.