Sensors: begin refactoring fetch/get #97965
Draft
Conversation
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
added 2 commits
October 21, 2025 00:55
Proof of concept for how to deprecate the fetch/get APIs by creating a single function that would handle converting a legacy request to an RTIO request and block while the request is processing. Signed-off-by: Yuval Peress <[email protected]>
Migrate a few samples in order to establish a new pattern to replace fetch/get. Signed-off-by: Yuval Peress <[email protected]>
yperess
force-pushed
the
yperess/refactor_fetch_get
branch
from
6f0b6f5 to
0fbe0cb
Compare
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Add a static function to replace the sensor fetch/get API and migrate several samples to kick off the deprecation effort.