Releases: wikirate/wikirate4py
Releases · wikirate/wikirate4py
2.0.6
2.0.5
Key Changes
🔧 API Client Refactors
- Introduce shared kwarg validation helpers (API._require, API._warn_unexpected)
- Refactor write endpoints to use explicit required/optional parameter lists
- Centralize query and filter parameter construction
- Improve filter handling and expand support for topics and topic frameworks
- Switch to a persistent requests.Session with:
- Session-wide headers and auth
- Context manager support for deterministic cleanup
- More robust request handling and file cleanup
- Improve logging and warnings for unexpected parameters
- Avoid shared mutable defaults in request helpers
🧩 Model Updates (Platform Alignment)
- Update Topic, Metric, and AnswerItem models to match current API responses
- Ensure compatibility with updated topic and topic framework structures
- Fix type validation and source parsing in detailed views
🧪 Tests & Fixtures
- Regenerate VCR cassettes to reflect current API behavior
- Apply minor test updates following API changes
2.0.4
2.0.3
2.0.2
Refactor: Code cleanup and nomenclature updates
- Thorough refactoring of multiple methods for improved readability, structure, and performance.
- Updated nomenclature: RelationshipAnswer(s) renamed to Relationship(s).
- Enhanced parameter validation and error handling.
- Improved documentation across key functions for clarity and consistency.
- Reduced redundancy in filter and parameter handling.
- Optimized API request methods and logging for easier debugging.
1.2.8
1.2.5
1.2.4
- Introduction of generate_url_key: Added a new function for creating URL-friendly string entity identifiers.
- Enhancements to get_answers method: Allows users to retrieve answers for Wikirate entities using both numeric and alphanumeric identifiers.
- Refactor and rename of get_relationship_answers_by_metric_id: Renamed to get_relationship_answers, enabling users to provide numeric or alphanumeric identifiers for entity retrieval of relevant relationship answers.
- Renaming of get_relationship_answers to get_relationship_metric_answers: Improved method naming for clarity.