Skip to content
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

Area units and conversion between metric and US #123563

Merged
merged 51 commits into from
Nov 21, 2024

Conversation

mikey0000
Copy link
Contributor

@mikey0000 mikey0000 commented Aug 11, 2024

Breaking change

Proposed change

Add Area units and conversions from metric to US customary

home-assistant/architecture#1124

Type of change

  • Dependency upgrade
  • Bugfix (non-breaking change which fixes an issue)
  • New integration (thank you!)
  • New feature (which adds functionality to an existing integration)
  • Deprecation (breaking change to happen in the future)
  • Breaking change (fix/feature causing existing functionality to break)
  • Code quality improvements to existing code or addition of tests

Additional information

This PR fixes the lack of conversion of area squared

Checklist

  • The code change is tested and works locally.
  • Local tests pass. Your PR cannot be merged unless tests pass
  • There is no commented out code in this PR.
  • I have followed the development checklist
  • I have followed the perfect PR recommendations
  • The code has been formatted using Ruff (ruff format homeassistant tests)
  • Tests have been added to verify that the new code works.

If user exposed functionality or configuration variables are added/changed:

If the code communicates with devices, web services, or third-party tools:

  • The manifest file has all fields filled out correctly.
    Updated and included derived files by running: python3 -m script.hassfest.
  • New or updated dependencies have been added to requirements_all.txt.
    Updated by running python3 -m script.gen_requirements_all.
  • For the updated dependencies - a link to the changelog, or at minimum a diff between library versions is added to the PR description.

To help with the load of incoming pull requests:

@mikey0000 mikey0000 requested a review from a team as a code owner August 11, 2024 04:01
Copy link

@home-assistant home-assistant bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There is a merge conflict.

@home-assistant home-assistant bot marked this pull request as draft August 11, 2024 04:01
@home-assistant
Copy link

Please take a look at the requested changes, and use the Ready for review button when you are done, thanks 👍

Learn more about our pull request process.

@mikey0000 mikey0000 changed the title area conversions Area units and conversion between metric and US Aug 11, 2024
@emontnemery
Copy link
Contributor

@mikey0000 CI checks are failing. Please fix that, and then make sure to click the "Ready for review" button to have your PR reviewed.

@emontnemery
Copy link
Contributor

@mikey0000 I don't see the rationale for adding the area converter. Which integrations will make use of this? I think there needs to be an approved architecture discussion first. If that's already the case, please link to it.

@mikey0000
Copy link
Contributor Author

mikey0000 commented Oct 22, 2024

@mikey0000 I don't see the rationale for adding the area converter. Which integrations will make use of this? I think there needs to be an approved architecture discussion first. If that's already the case, please link to it.

All lawn mower integrations use area squared, added the architecture discussion link

@emontnemery
Copy link
Contributor

emontnemery commented Oct 23, 2024

Thanks @mikey0000 for adding the link to the architecture proposal 👍

However, just adding a utility function for converting areas is not enough for integrations - and users - to benefit. You'll also need to add a new sensor device class, and add preferred area units to the metric and us customary unit systems.

Here's an example of a more complete PR, although it did not add preferred conductivity units to the unit systems: #118728
This is an example of a PR adding preferred units to the unit systems: https://github.com/home-assistant/core/pull/90504/files

@mikey0000
Copy link
Contributor Author

Thanks @mikey0000 for adding the link to the architecture proposal 👍

However, just adding a utility function for converting areas is not enough for integrations - and users - to benefit. You'll also need to add a new sensor device class, and add preferred area units to the metric and us customary unit systems.

Here's an example of a more complete PR, although it did not add preferred conductivity units to the unit systems: #118728 This is an example of a PR adding preferred units to the unit systems: https://github.com/home-assistant/core/pull/90504/files

Thanks, I'll update it. Thanks also for the reply on the Architecture discussion.

Copy link

coderabbitai bot commented Oct 23, 2024


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?

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

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)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

@emontnemery
Copy link
Contributor

@mikey0000 the architecture proposal is approved 👍
There are quite a lot of places which need to be updated when adding a new sensor device class with unit conversion, feel free to reach out on Discord if anything is unclear. My nick there is @emontnemery

@mikey0000
Copy link
Contributor Author

@mikey0000 the architecture proposal is approved 👍 There are quite a lot of places which need to be updated when adding a new sensor device class with unit conversion, feel free to reach out on Discord if anything is unclear. My nick there is @emontnemery

Thanks I really appreciate the support, see you in the code owners channel 😄

@gjohansson-ST
Copy link
Member

Marked the PR as draft as there is quite a bit of conflicts that needs to be sorted.

    "tsconfig-paths-webpack-plugin": "^4.1.0",
@mikey0000 mikey0000 marked this pull request as ready for review November 9, 2024 23:32
@mikey0000
Copy link
Contributor Author

Marked the PR as draft as there is quite a bit of conflicts that needs to be sorted.

Sorted

@mikey0000
Copy link
Contributor Author

Not sure why one test is timing out.

Copy link
Contributor

@emontnemery emontnemery left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice, thanks @mikey0000 👍

Copy link
Member

@gjohansson-ST gjohansson-ST left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM 👍

@emontnemery
Copy link
Contributor

@mikey0000
Copy link
Contributor Author

Please open and link to documentation PRs for:

* https://developers.home-assistant.io/docs/core/entity/number

* https://developers.home-assistant.io/docs/core/entity/sensor

* A dev blog post

* https://next.home-assistant.io/integrations/number/

* https://next.home-assistant.io/integrations/sensor/

added

jpbede
jpbede previously requested changes Nov 14, 2024
Copy link
Member

@jpbede jpbede left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Some conflicts appeared, could you have a look?

@home-assistant home-assistant bot marked this pull request as draft November 14, 2024 18:47
@mikey0000 mikey0000 marked this pull request as ready for review November 14, 2024 19:31
@emontnemery emontnemery merged commit d854940 into home-assistant:dev Nov 21, 2024
64 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants