Add external queries for records and statistics - #501
Merged
Merged
Conversation
Owner
|
Looks good! Thank you very much. |
Contributor
Author
|
Happy to help! 🫶🏻 |
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.
Adds two broadcast queries, mirroring the Wear API as per our discussion in #452:
Both take an optional shift extra (days from today, 0 = today) and answer with a JSON broadcast. Statistics also take a filter type (activity, category or tag). They respect the "receive queries" setting.
The records and statistics logic from the Wear API is now in a shared WearQueryInteractor in core, so the watch and these queries return the same data.
I also listed both queries in the automation help screen.