-
Notifications
You must be signed in to change notification settings - Fork 399
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: add status
column to records
table
#5059
feat: add status
column to records
table
#5059
Conversation
…te schema in datasets context
…e-datasets-distribution
…/create-datasets-with-distribution
for more information, see https://pre-commit.ci
…e-datasets-distribution
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## feat/create-datasets-with-distribution #5059 +/- ##
===========================================================================
+ Coverage 61.16% 91.98% +30.82%
===========================================================================
Files 328 136 -192
Lines 17683 5855 -11828
===========================================================================
- Hits 10815 5386 -5429
+ Misses 6868 469 -6399
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
…/create-datasets-with-distribution
…e-datasets-distribution
…-to-records-table
…e-datasets-distribution
…-to-records-table
…5028) # Description This PR add changes to support update dataset distribution settings. Allowing for example to update `min_submitted` attribute when `overlap` distribution strategy is in use. Closes #5010 **Type of change** (Please delete options that are not relevant. Remember to title the PR according to the type of change) - [ ] Bug fix (non-breaking change which fixes an issue) - [x] New feature (non-breaking change which adds functionality) - [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected) - [ ] Refactor (change restructuring the codebase without changing functionality) - [ ] Improvement (change adding some improvement to an existing functionality) - [ ] Documentation update **How Has This Been Tested** (Please describe the tests that you ran to verify your changes. And ideally, reference `tests`) - [x] Adding new tests. **Checklist** - [ ] I added relevant documentation - [ ] follows the style guidelines of this project - [ ] I did a self-review of my code - [ ] I made corresponding changes to the documentation - [ ] My changes generate no new warnings - [ ] I have added tests that prove my fix is effective or that my feature works - [ ] I filled out [the contributor form](https://tally.so/r/n9XrxK) (see text above) - [ ] I have added relevant notes to the CHANGELOG.md file (See https://keepachangelog.com/) --------- Co-authored-by: Paco Aranda <francis@argilla.io>
…tatus-to-records-table
Description
This PR include changes to add a new
status
column torecords
table with the following details:status
column arepending
andcompleted
.status
value.status
column will have thepending
value. (Showing that the record is still pending of being annotated).submitted
status will be updated frompending
tocompleted
.Closes #5058
Type of change
(Please delete options that are not relevant. Remember to title the PR according to the type of change)
How Has This Been Tested
(Please describe the tests that you ran to verify your changes. And ideally, reference
tests
)Checklist