Add special behaviour for 'composed' price sensors #70
Conversation
This file contains 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
and handle 'sensor dependencies' instead, to download all necessary API sensors for the enabled 'sensor keys'
now getting 6 sensors with token
azogue
changed the title
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.
cc @MiguelAngelLV
Follow up #69 with changes to avoid API calls for 'composed' sensors and, instead, use a 'api-sensor' dependency concept, to download the necessary API indicators for all enabled sensors (composed or not), and nothing more.
Also, some cleaning of old fixtures, update of linters, minor bugfixes, and bump version for new release 🚀