explicit export source for object classification #119
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
in the past nothing was passed to the workflow, which defaulted to `Object Predictions` output. This makes it explicit and fixes the previous binding to input type. While it would be cool to choose the export source, and we should definitely do it, see #64.
k-dominik
force-pushed
the
fix-oc-command
branch
from
3f709b8
to
65c6d4f
Compare
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.
in the past nothing was passed to the workflow, which defaulted to
Object Predictionsoutput.This makes it explicit and fixes the previous binding to input type. While it would be cool to choose the export source, and we should definitely do it, see #64.