Removed _emptyIteratorStopper from response #89
Merged
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
|
Hi, |
|
Awesome! Thanks! |
mabunixda
pushed a commit
that referenced
this pull request
Mar 4, 2021
* Removed _emptyIteratorStopper from response * Fix big if no lights are configured Co-authored-by: Claudio Chimera <Claudio.Chimera@gmail.com> Signed-off-by: Martin Buchleitner <mbuchleitner@infralovers.com>
mabunixda
added a commit
that referenced
this pull request
Mar 4, 2021
* npm-update: fix: revert linting script fix: ci gh action fix: allow linting bypass argument 1 feat: update to semantic versioning fix: upgrade mustache from 4.0.1 to 4.1.0 (#85) Removed _emptyIteratorStopper from response (#89) Changed the request info message to debug (#86) Bump ini from 1.3.5 to 1.3.7
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.
Hi,
I've removed the _emptyIteratorStopper from the response and fixed a small bug where the on status was not filled.
Claudio