Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Remove input_channel argument from ValueConsumer #706

Closed
wants to merge 103 commits into from

Conversation

mairas
Copy link
Collaborator

@mairas mairas commented Jun 16, 2024

ValueConsumer input_channels were implemented to allow multiple inputs to a single transform. However, the semantics were never fully thought out, and the argument was used very rarely. Since you can achieve the same result by adding multiple LambdaConsumers in a single class, I've decided to remove the input_channel argument altogether. This might break some transforms temporarily.

mairas and others added 28 commits May 25, 2024 20:27
Rename ConstantSensor getters and setters
Unsupported since v1...
Use native ESP-IDF logging
This make connect_to and O(N) operation with respect to the
number of existing observers, but the call order of the observers
is now the same as the insertion order. Also, adding new observers
usually happens in the setup stage of program execution, in which
the added performance penalty is not relevant.
Throttle limits the update rate of its input.
This might break some transforms.
@mairas
Copy link
Collaborator Author

mairas commented Jun 16, 2024

Wrong destination branch.

@mairas mairas closed this Jun 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant