State data recording fixes #23
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
Closed
JamesArruda
added a commit
that referenced
this pull request
Jan 3, 2025
* Docs for data gathering. Updates for usability an clarity. * Updating NamedEntity and Monitoring resources to assist data gathering. * New docs for new features. Updated other docs for new features. * Making states initialize to default right away to correct data gathering bugs. (#23) * Location data object improvements. (#24)
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.
Actorhas the state set the default right awayDetectabilityStatebug revealed by changes. The motion manager call happened when the initial state setting went to the recording method, but that's a case where the motion manager doesn't need to know.