feat: add optional Qveris market data source - #192
Draft
Leon-Drq wants to merge 1 commit into
Draft
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.
What
Add an optional
QverisDataSourcein front of QuantDinger's existing market providers.Why
QuantDinger currently integrates several provider-specific data sources. Qveris can provide one optional discovery and execution layer across markets, while preserving all current providers and behavior. This gives deployments another way to obtain structured financial data without making Qveris required or exclusive.
Configuration
The integration is disabled by default. It is enabled only when both values are set:
See
docs/integrations/QVERIS_DATA_SOURCE.mdfor all settings and verification steps.Backward compatibility
get_klineandget_tickercallers and normalized response shapes are unchanged.Testing
Commands run:
The adapter-specific tests cover discovery metadata variants, market-aware tool selection, parameter mapping, three OHLCV response layouts, ticker normalization, opt-in configuration, factory wrapping, and automatic fallback.
Live smoke test
A live request was run with
USStock,AAPL,1D, andlimit=5using a configured Qveris key:eodhd.eod_historical_data.retrieve.v1.a43f3b91Review notes
This is intentionally a Draft PR so the maintainers can confirm the integration direction before it is marked ready. I am happy to adjust naming, configuration, or provider placement to match the project's preferences.