fix(client): determine the last_id by finding the maximum Id in the list#156
Merged
fix(client): determine the last_id by finding the maximum Id in the list#156
last_id by finding the maximum Id in the list#156Conversation
Pull Request Test Coverage Report for Build 14421885397Details
💛 - Coveralls |
palazzem
force-pushed
the
palazzem/fix-154
branch
from
1c845fe to
d7632db
Compare
Merged
3 tasks
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
2 participants
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.
Related Issues
last_idkey for sectors, inputs and outputs doesn't point to the right last ID #154Proposed Changes:
This change removes the assumption that items ID returned from the Cloud API, are ordered.
Testing:
Home Assistant integration polling should work again.
Extra Notes (optional):
n/a
Checklist