Skip to content

Lovelace: add confirmation action#10834

Merged
frenck merged 3 commits into
home-assistant:nextfrom
iantrich:confirm-action
Oct 20, 2019
Merged

Lovelace: add confirmation action#10834
frenck merged 3 commits into
home-assistant:nextfrom
iantrich:confirm-action

Conversation

@iantrich
Copy link
Copy Markdown
Member

Description:

home-assistant/frontend#4006

Checklist:

  • Branch: next is for changes and new documentation that will go public with the next Home Assistant release. Fixes, changes and adjustments for the current release should be created against current.
  • The documentation follows the standards.

@iantrich iantrich self-assigned this Oct 16, 2019
@probot-home-assistant probot-home-assistant Bot added has-parent This PR has a parent PR in another repo next This PR goes into the next branch Hacktoberfest An PR on this issue (or the PR itself) is eligible towards Hacktoberfest! labels Oct 16, 2019
@iantrich iantrich added the new-feature This PR adds documentation for a new Home Assistant feature to an existing integration label Oct 16, 2019
@iantrich iantrich added the parent-merged The parent PR has been merged already label Oct 16, 2019
@iantrich
Copy link
Copy Markdown
Member Author

Is there a better way to do this? Repeating the same lines throughout all these files seems prone to failure and makes maintenance a chore.

Comment thread source/_includes/asides/lovelace_navigation.html Outdated
required: false
description: "Present a confirmation dialog to confirm the action. See `confirmation` object below"
type: [boolean, map]
default: "false"
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.

You don't have to quote booleans ;)

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

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

All other defaults in this file had quotes, so I followed the trend 🤷‍♂

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.

👍 I know! It's weird! 😉

@frenck frenck added the in-progress This PR/Issue is currently being worked on label Oct 17, 2019
@frenck frenck removed the in-progress This PR/Issue is currently being worked on label Oct 20, 2019
@frenck frenck merged commit 6882906 into home-assistant:next Oct 20, 2019
@probot-home-assistant probot-home-assistant Bot removed the parent-merged The parent PR has been merged already label Oct 20, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Hacktoberfest An PR on this issue (or the PR itself) is eligible towards Hacktoberfest! has-parent This PR has a parent PR in another repo new-feature This PR adds documentation for a new Home Assistant feature to an existing integration next This PR goes into the next branch

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants