Cleanup: Rename class Account to Zaptec#196
Merged
sveinse merged 2 commits intocustom-components:masterfrom Jul 16, 2025
Merged
Cleanup: Rename class Account to Zaptec#196sveinse merged 2 commits intocustom-components:masterfrom
sveinse merged 2 commits intocustom-components:masterfrom
Conversation
* Rename members from self._account to self.zaptec in Installation and Charger objects * Rename self.account in ZaptecFlowHandler
Collaborator
Author
|
I reviewed it a second time, and I think it looks good. Moving forward. |
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.
This PR contains the rename of
class Accounttoclass Zaptecto make it more descriptive and consistent. This is a part of a series of cleanups to improve the API for the Zaptec facing API.NOTE This is technically a API change, but since the only consumers of the API are the HA integration, this should be fine. The PR does not contain any functional change.