-
-
Notifications
You must be signed in to change notification settings - Fork 896
UI: add unit property #21396
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
UI: add unit property #21396
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hey @andig - I've reviewed your changes and they look great!
Here's what I looked at during the review
- 🟢 General issues: all looks good
- 🟢 Security: all looks good
- 🟢 Testing: all looks good
- 🟢 Complexity: all looks good
- 🟢 Documentation: all looks good
Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.
Generated doc examples: Vehicle
Meter
Note: |
I'd say we leave it as is. Currently Config UI converts duration fields to a second input field. In some special cases (e.g. enable/disable delay) it's shown as minute inputs. For now I think this is ok. We can decide to introduce ( |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hey @andig - I've reviewed your changes - here's some feedback:
- I noticed some params (e.g. in pulsatrix.yaml) dropped their
description
block when converting tohelp
-only—since the template still expects adescription
, please re-add it or adjust the template to avoid missing labels. - Please add or extend an end-to-end test that verifies the new
unit
prop is actually displayed in the UI for at least one field, to catch any integration gaps inPropertyField
. - With so many YAML entries now having a
unit
, consider centralizing or templating the common unit definitions to reduce duplication and cut down on manual errors.
Here's what I looked at during the review
- 🟢 General issues: all looks good
- 🟢 Security: all looks good
- 🟢 Testing: all looks good
- 🟢 Complexity: all looks good
- 🟢 Documentation: all looks good
Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.
@naltatis fehlt das evtl. noch bei den Demo Devices? |
Refs #21352 (comment)
TODO
configure
@andig