Skip to content

Add an approach for determining if a dataclass field is supported #2452

Add an approach for determining if a dataclass field is supported

Add an approach for determining if a dataclass field is supported #2452

Triggered via pull request January 8, 2026 06:15
Status Failure
Total duration 52s
Artifacts

ci.yml

on: pull_request
Matrix: test
Lint Commit Messages
15s
Lint Commit Messages
lint
13s
lint
Build Package
10s
Build Package
Test Semantic Release
50s
Test Semantic Release
release
0s
release
Fit to window
Zoom out
Zoom in

Annotations

2 errors
lint
Process completed with exit code 1.
Lint Commit Messages
You have commit messages with errors ⧗ input: 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. ✖ 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