Releases: power-edge/pymlb_statsapi
Releases · power-edge/pymlb_statsapi
Release v1.4.3
fix: Draft.draftPicks() now correctly uses year parameter in URL path
- Fixed path template in draft.json schema: /v1/draft -> /v1/draft/{year}
- Fixed path config in endpoint-model.json: /v1/draft -> /v1/draft/{year}
- Added BDD tests for Draft endpoint (draftPicks, draftProspects, latestDraftPicks)
- Added gzipped stubs for Draft tests
The draftPicks method was ignoring the year parameter and always returning
current year's data. Now correctly constructs URL like /v1/draft/2020.
Fixes #5
Release v1.1.0
feat: finalize library with ETL exports and entity relationship examples
- Add entity relationships example showing data flow patterns
- Create schema export utilities for ETL pipeline generation
- Simplify README to focus on API wrapper functionality
- Generate machine-readable endpoint and ETL mapping schemas
- Remove ETL-specific ERD (moved to separate mlb-etl-datamart project)
- All tests passing (98 unit tests, 39 BDD scenarios)
Release v1.4.2
test: achieve 97.24% coverage with comprehensive test suite
Add 68 new tests across 7 test files to increase coverage from 68.20% to 97.24%.
New test files:
- test_api_response_storage.py: File I/O, path generation, gzip, metadata (15 tests)
- test_endpoint_method_introspection.py: Schema introspection, parameters, docs (11 tests)
- test_registry_errors.py: Registry error handling and caching (5 tests)
- test_http_retry.py: HTTP retry logic, backoff, error handling (7 tests)
- test_edge_cases.py: Property accessors, validation, enum handling (17 tests)
- test_final_coverage.py: Parent dirs, repr, case-insensitive enums (6 tests)
- test_complete_coverage.py: Wrappers, formatters, factory functions (7 tests)
Coverage achievements:
- 100% coverage: registry.py, log.py, schema_loader.py, all init.py
- 96.51% coverage: factory.py (only defensive code paths uncovered)
- Overall: 97.24% (505 statements, 98 passing tests)
Remaining 2.76% uncovered consists of defensive code paths that cannot
be triggered without breaking the API contract.
Release v1.4.1
chore: remove obsolete setup.cfg and update environment configs
- Remove setup.cfg (legacy file, using pyproject.toml + hatch-vcs)
- Update pypi environment to allow custom branch policies (permits tags)
- This enables version tags to trigger PyPI releases