-
-
Notifications
You must be signed in to change notification settings - Fork 32.3k
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
Use common strings in life360 config flow #42375
Use common strings in life360 config flow #42375
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.
Thanks!
Tests for the config flow are missing. 🙈 |
Working on it asap 😅 |
That would be great! We can merge here when the build passes. |
Actually I cannot find any tests for this integration 😆 |
Yeah, that was what I meant. |
Oh sorry misunderstood what you meant by missing. |
Yeah, this PR is ok. We don't need to add any tests here. |
* Use common strings for life360 config flow * Address feedback comments * Keep two space indentation * Fix indentation hopefully
Breaking change
Proposed change
Use common strings in life360 config flow as described in #40578
Type of change
Example entry for
configuration.yaml
:# Example configuration.yaml
Additional information
Checklist
black --fast homeassistant tests
)If user exposed functionality or configuration variables are added/changed:
If the code communicates with devices, web services, or third-party tools:
Updated and included derived files by running:
python3 -m script.hassfest
.requirements_all.txt
.Updated by running
python3 -m script.gen_requirements_all
..coveragerc
.The integration reached or maintains the following Integration Quality Scale:
To help with the load of incoming pull requests: