[QQC-755] Allow to pass batch consensus settings when creating a batch #736
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
mkozik-lb
force-pushed
the
mkozik/batch-consensus-settings
branch
from
fa68719 to
ea9a549
Compare
mkozik-lb
commented
Oct 27, 2022
labelbox/schema/project.py
Outdated
Comment on lines
608
to
609
| consensus_settings_dict = consensus_settings.dict( | ||
| ) if consensus_settings else None |
Contributor
Author
There was a problem hiding this comment.
I don't want to fight the formatting here, but it's a pretty bad default rule ☝️
mkozik-lb
force-pushed
the
mkozik/batch-consensus-settings
branch
from
67a131a to
f50aa74
Compare
msokoloff1
approved these changes
Nov 1, 2022
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.
Tandem PR in API that needs to be merged before this: https://github.com/Labelbox/intelligence/pull/11383 (done)
This is part of project paradigm which is set to release on 2nd November. As part of the changes, we'll prefer customers to provide consensus settings per batch, rather than per project.
Updates to our SDK documentation are coming after this PR gets in.