refactor!: Split HassWSApi
into resource-specific classes
#18
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.
Overview
This PR refactors the existing monolithic
HassWSApi
class by extracting resource-specific methods into dedicated API classes. This improves code organization, maintainability, and makes the codebase more modular while maintaining the same functionality.The methods previously available directly on
HassWSApi
have been moved to their respective API classes. All calls need to be updated to use the new structure:New API Classes
Moved existing functionality into these dedicated classes:
Implementation Details
ResourceApi
base classHassClientWebSocket
in constructorHassWSApi
classWebSocket
communicationTesting
Documentation
Version Update
Due to breaking changes, this requires a major version bump:
Migration Guide
HassWSApi