Repository navigation
Add cameras field to vision service - #920
Draft
Devin T. Currie (DTCurrie) wants to merge 2 commits into
Draft
Devin T. Currie (DTCurrie) wants to merge 2 commits into
Devin T. Currie (DTCurrie) wants to merge 2 commits into
Conversation
Devin T. Currie (DTCurrie)
added
the
ready-for-protos
This was referenced Oct 8, 2026
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.
Modular vision service APIs work only with cameras declared as dependencies. We don't have an API that tells clients which cameras those dependencies are.
This PR introduces a
repeated string camerasfield to the vision service'sGetPropertiesResponseto provide that information.If a modular author returns an empty array, we assume there are no strict limits on what cameras can be used.
Related PRs: