feat(analysis): add FXMacroData release calendar integration - #46
Draft
roberttidball wants to merge 2 commits into
Draft
feat(analysis): add FXMacroData release calendar integration#46roberttidball wants to merge 2 commits into
roberttidball wants to merge 2 commits into
Conversation
roberttidball
changed the title
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
1 participant
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 changed? Why?
Adds a small, read-only FXMacroData helper for prediction-market studies that need official-source macro release-calendar context. The helper fetches scheduled macro releases from the public FXMacroData calendar endpoint, caps requested rows, and exposes upcoming tier-filtered events that can be joined to Kalshi or Polymarket workflows.
Notes to reviewers
Key files changed:
src/common/fxmacrodata.py: FXMacroData release-calendar helper functions.The integration uses only the Python standard library and keeps API-key use optional via
FXMACRODATA_API_KEYor an explicit function argument.How has it been tested?
python -m ruff check .python -m ruff format --check .python -m pytest tests/test_compile.py::test_module_imports -q -k fxmacrodatagit diff --checkFull
python -m pytest tests/ -qwas attempted locally, but this environment is missing optional dependencies used by unrelated modules (web3,squarify). The repository's CI usesuv sync --group dev, which should install those dependencies.