Skip to content

Add an approach for determining if a dataclass field is supported (#740) #2463

Add an approach for determining if a dataclass field is supported (#740)

Add an approach for determining if a dataclass field is supported (#740) #2463

Triggered via push January 10, 2026 15:40
Status Failure
Total duration 2m 20s
Artifacts

ci.yml

on: push
Matrix: test
Lint Commit Messages
15s
Lint Commit Messages
lint
18s
lint
Build Package
0s
Build Package
Test Semantic Release
0s
Test Semantic Release
Fit to window
Zoom out
Zoom in

Annotations

1 error and 1 notice
Lint Commit Messages
You have commit messages with errors ⧗ input: Add an approach for determining if a dataclass field is supported (#740) * feat: Add an approach for determining if a dataclass field is supported This consists of multiple concepts: - DeviceFeaturesTrait defines a method `is_field_supported` which will tell you if an optional field on a RoborockBase class type is supported or not - The RoborockBase field defins a metadata attribute for a product schea code which is used to check the field against some other source - We could substitue in other values in DeviceFeatures or status in the future as needed. This adds 6 fields that are straight forward to add. * chore: update test descrition * chore: simplify supported_schema_codes * chore: update pydoc for DeviceFeaturesTrait * chore: Update to use StrEnum * chore: add function to create field metadata ✖ subject may not be empty [subject-empty] ✖ type may not be empty [type-empty] ✖ found 2 problems, 0 warnings ⓘ Get help: https://github.com/conventional-changelog/commitlint/#what-is-commitlint
release
Generating and uploading digital attestations