Add blog and update number and sensor entity docs #2448
Conversation
mikey0000
force-pushed
the
area-square-meters-docs
branch
from
72f08a3
to
d64b059
Compare
📝 Walkthrough📝 WalkthroughWalkthroughThe changes introduce new documentation and modifications related to area units in Home Assistant Core 2024.12. A new file details the deprecation of the Changes
📜 Recent review detailsConfiguration used: CodeRabbit UI 📒 Files selected for processing (1)
🚧 Files skipped from review as they are similar to previous changes (1)
Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media? 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 4
🧹 Outside diff range and nitpick comments (2)
blog/2024-12-04-area-squared-units.md (1)
4-4: Consider a more descriptive titleThe current title "Area squared unit enumerators" could be more specific. Consider: "Home Assistant: Introducing area unit enumerators"
docs/core/entity/number.md (1)
36-36: Minor: Consider removing trailing pipe for consistent markdown style.The table row contains a trailing pipe character which differs from the recommended markdown style. While this doesn't affect rendering, consider removing it for consistency.
-| `NumberDeviceClass.AREA` | m², cm², km², mm², in², ft², yd², mi², ac, ha | Area | +| `NumberDeviceClass.AREA` | m², cm², km², mm², in², ft², yd², mi², ac, ha | Area🧰 Tools
🪛 Markdownlint
36-36: Expected: leading_only; Actual: leading_and_trailing; Unexpected trailing pipe
Table pipe style(MD055, table-pipe-style)
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
📒 Files selected for processing (3)
blog/2024-12-04-area-squared-units.md(1 hunks)docs/core/entity/number.md(1 hunks)docs/core/entity/sensor.md(1 hunks)
🧰 Additional context used
📓 Path-based instructions (1)
blog/2024-12-04-area-squared-units.md (6)
Pattern */**(html|markdown|md): - For instructional content in documentation, use a direct and authoritative tone. Avoid expressions of politeness such as 'may' or 'please', and ensure the goal of the instruction is fronted.
- Apply the Microsoft Style Guide to ensure documentation maintains clarity and conciseness.
- In step-by-step instructions, front the location phrase in the instructional sentence.
- In step-by-step instructions, front the 'goal' in the instructional sentence.
- In step-by-step instructions, if in doubt what to front, front the 'goal' before the location phrase in the instructional sentence.
- do not hyphenate terms like 'top-right' or 'bottom-left' with 'corner'
Pattern */**(html|markdown|md): - Use bold to mark UI strings.
- If "" are used to mark UI strings, replace them by bold.
Pattern */**(html|markdown|md): - Be brief in your replies and don't add fluff like "thank you for..." and "Please let me know if"
Pattern */**(html|markdown|md): - Use sentence-style capitalization also in headings.
Pattern */**(html|markdown|md): do not comment on HTML used for icons
Pattern */**(html|markdown|md): Avoid flagging inline HTML for embedding videos in future reviews for this repository.
🪛 Markdownlint
blog/2024-12-04-area-squared-units.md
10-10: Expected: 0; Actual: 2
Unordered list indentation
(MD007, ul-indent)
docs/core/entity/number.md
36-36: Expected: leading_only; Actual: leading_and_trailing; Unexpected trailing pipe
Table pipe style
(MD055, table-pipe-style)
🔇 Additional comments (2)
docs/core/entity/number.md (1)
36-36: LGTM! Comprehensive area units coverage.
The new NumberDeviceClass.AREA is well-documented with a complete set of supported units covering both metric and imperial measurements.
🧰 Tools
🪛 Markdownlint
36-36: Expected: leading_only; Actual: leading_and_trailing; Unexpected trailing pipe
Table pipe style
(MD055, table-pipe-style)
docs/core/entity/sensor.md (1)
37-38: Verify supported area units
Let's verify that the documented units align with the implementation in Home Assistant Core.
MartinHjelmare
changed the title
|
Please take a look at the requested changes, and use the Ready for review button when you are done, thanks 👍 |
Co-authored-by: epenet <[email protected]>
Co-authored-by: epenet <[email protected]>
There was a problem hiding this comment.
Actionable comments posted: 2
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
📒 Files selected for processing (2)
blog/2024-12-04-area-squared-units.md(1 hunks)docs/core/entity/sensor.md(1 hunks)
🚧 Files skipped from review as they are similar to previous changes (1)
- docs/core/entity/sensor.md
🧰 Additional context used
📓 Path-based instructions (1)
blog/2024-12-04-area-squared-units.md (6)
Pattern */**(html|markdown|md): - For instructional content in documentation, use a direct and authoritative tone. Avoid expressions of politeness such as 'may' or 'please', and ensure the goal of the instruction is fronted.
- Apply the Microsoft Style Guide to ensure documentation maintains clarity and conciseness.
- In step-by-step instructions, front the location phrase in the instructional sentence.
- In step-by-step instructions, front the 'goal' in the instructional sentence.
- In step-by-step instructions, if in doubt what to front, front the 'goal' before the location phrase in the instructional sentence.
- do not hyphenate terms like 'top-right' or 'bottom-left' with 'corner'
Pattern */**(html|markdown|md): - Use bold to mark UI strings.
- If "" are used to mark UI strings, replace them by bold.
Pattern */**(html|markdown|md): - Be brief in your replies and don't add fluff like "thank you for..." and "Please let me know if"
Pattern */**(html|markdown|md): - Use sentence-style capitalization also in headings.
Pattern */**(html|markdown|md): do not comment on HTML used for icons
Pattern */**(html|markdown|md): Avoid flagging inline HTML for embedding videos in future reviews for this repository.
🪛 LanguageTool
blog/2024-12-04-area-squared-units.md
[uncategorized] ~22-~22: You might be missing the article “the” here.
Context: ...ntity/number#available-device-classes) Sensor entity has the addition of `SensorDevic...
(AI_EN_LECTOR_MISSING_DETERMINER_THE)
Co-authored-by: epenet <[email protected]>
Co-authored-by: epenet <[email protected]>
Co-authored-by: epenet <[email protected]>
There was a problem hiding this comment.
Actionable comments posted: 1
🧹 Outside diff range and nitpick comments (1)
blog/2024-12-04-area-squared-units.md (1)
16-16: Enhance the AreaConverter introductionThe current introduction of AreaConverter is abrupt. Consider providing more context about when developers would need to use it directly, given that automatic conversion is available through the device class.
-Area units can also be converted between us customary and metric units using `AreaConverter` +While the device class handles unit conversion automatically, custom conversions between US customary and metric units can be performed using `AreaConverter` when needed.
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
📒 Files selected for processing (1)
blog/2024-12-04-area-squared-units.md(1 hunks)
🧰 Additional context used
📓 Path-based instructions (1)
blog/2024-12-04-area-squared-units.md (6)
Pattern */**(html|markdown|md): - For instructional content in documentation, use a direct and authoritative tone. Avoid expressions of politeness such as 'may' or 'please', and ensure the goal of the instruction is fronted.
- Apply the Microsoft Style Guide to ensure documentation maintains clarity and conciseness.
- In step-by-step instructions, front the location phrase in the instructional sentence.
- In step-by-step instructions, front the 'goal' in the instructional sentence.
- In step-by-step instructions, if in doubt what to front, front the 'goal' before the location phrase in the instructional sentence.
- do not hyphenate terms like 'top-right' or 'bottom-left' with 'corner'
Pattern */**(html|markdown|md): - Use bold to mark UI strings.
- If "" are used to mark UI strings, replace them by bold.
Pattern */**(html|markdown|md): - Be brief in your replies and don't add fluff like "thank you for..." and "Please let me know if"
Pattern */**(html|markdown|md): - Use sentence-style capitalization also in headings.
Pattern */**(html|markdown|md): do not comment on HTML used for icons
Pattern */**(html|markdown|md): Avoid flagging inline HTML for embedding videos in future reviews for this repository.
🔇 Additional comments (1)
blog/2024-12-04-area-squared-units.md (1)
7-10: LGTM!
The summary effectively communicates the key changes and follows documentation guidelines.
Co-authored-by: epenet <[email protected]>
Co-authored-by: epenet <[email protected]>
Proposed change
Add Area documentation
Type of change
Additional information
Summary by CodeRabbit
New Features
NumberDeviceClass.AREA, for thenumberentities, supporting various area units.SensorDeviceClass.AREA, for thesensorentities, supporting various area units.AreaConverter.Documentation
numberandsensorentities to reflect the new device classes and clarify state restoration instructions.AREA_SQUARE_METERSand guidance for transitioning toUnitOfArea.SQUARE_METERS.