Skip to content

Display alert entity row as a toggle#2138

Merged
balloob merged 2 commits intohome-assistant:devfrom
pprazzi:patch-1
Nov 29, 2018
Merged

Display alert entity row as a toggle#2138
balloob merged 2 commits intohome-assistant:devfrom
pprazzi:patch-1

Conversation

@pprazzi
Copy link
Copy Markdown
Contributor

@pprazzi pprazzi commented Nov 28, 2018

In the default UI alerts where displayed as toggles, this change makes this also the default behaviour in Lovelace

In the default UI alerts where displayed as toggles, this change makes this also the default behaviour in Lovelace
@homeassistant
Copy link
Copy Markdown
Contributor

Hi @pprazzi,

It seems you haven't yet signed a CLA. Please do so here.

Once you do that we will be able to review and accept this pull request.

Thanks!

]);
const DOMAIN_TO_ELEMENT_TYPE = {
automation: "toggle",
alert: "toggle",
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

keep it alphabetical

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

sorry, updated PR

@iantrich
Copy link
Copy Markdown
Member

I want to test how this behaves before approving as you noted in the Discord chat this is untested.

@iantrich iantrich changed the title Update create-row-element.js Display alert entity row as a toggle Nov 29, 2018
@iantrich
Copy link
Copy Markdown
Member

I did verify that this is working as intended on my dev environment.

Going to leave it till tomorrow to see if anyone objects to this way of representing the alert row

@balloob balloob merged commit a249289 into home-assistant:dev Nov 29, 2018
@ghost ghost removed the in progress label Nov 29, 2018
@pprazzi pprazzi deleted the patch-1 branch November 30, 2018 12:07
@balloob balloob mentioned this pull request Dec 5, 2018
@github-actions github-actions bot locked and limited conversation to collaborators Jul 7, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants