Fixed improper JSON response from apis that use quote summary #331
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 calling any quoteSummary-based property (such as asset_profile, earnings, financial_data, key_stats, etc.) via the yahooquery package, the returned values exhibit inconsistent response structures depending on the ticker and asset type:
This systematic inconsistency affects 15 out of 17 quoteSummary properties and causes downstream code that expects consistent dict-of-dicts structures to fail or misinterpret responses across different asset classes.
Real-world Impact
This GitHub Actions run is a real-world example of someone expecting a parsable JSON response yet receiving an unexpected response from the API.
https://github.com/JNewman-cell/StockInformationWebsiteGithubActions/actions/runs/18789336097/job/53615494426
Behavior
Old Response: {'EAI': 'No fundamentals data found for symbol: EAI'}
New Response: { "error": { "code": 404, "type": "NotFoundError", "message": "No fundamentals data found for symbol: EAI", "symbol": "EAI" } }