Group classification type

[Tim-Kerr]

Description

Added a new "group" type for classifications.

Fixes # (issue)

Type of change

Please delete options that are not relevant.

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Document change (fix typo or modifying any markdown files, code comments or anything in the examples folder only)

All Submissions

• Have you followed the guidelines in our Contributing document?
• Have you provided a description?
• Are your changes properly formatted?

New Feature Submissions

• Does your submission pass tests?
• Have you added thorough tests for your new feature?
• Have you commented your code, particularly in hard-to-understand areas?
• Have you added a Docstring?

Changes to Core Features

• Have you written new tests for your core changes, as applicable?
• Have you successfully run tests with your changes locally?
• Have you updated any code comments, as applicable?

---

Note

Introduces support for group classifications.

• Adds GROUP to Classification.Type in classification.py
• No changes to option requirements (_REQUIRES_OPTIONS remains checklist/radio)

^{Written by Cursor Bugbot for commit a43a728. This will update automatically on new commits. Configure here.}

[lb-pno]

LGTM

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{Bugbot Autofix is OFF. To automatically fix reported issues with Cloud Agents, enable Autofix in the Cursor dashboard.}

[cursor]

GROUP classification type may need options requirement

Medium Severity

The new GROUP classification type is not added to _REQUIRES_OPTIONS, allowing creation of GROUP classifications without any options. Semantically, a "group" implies grouping items together, which would require options to be meaningful. An empty GROUP classification (with nothing to group) may result in invalid ontologies or unexpected behavior during labeling. If GROUP is intended to behave like CHECKLIST/RADIO, it needs to be added to _REQUIRES_OPTIONS.

Additional Locations (1)

• libs/labelbox/src/labelbox/schema/tool_building/classification.py#L65-L66