Use explicit links inside configuration blocks (#11645)

The converter used in the configuration plugin is not aware of
references declared outside of the block and therefore fails to render
reference links. This replaces them with explicit links.

Resolves #11643
This commit is contained in:
Felix Eckhofer 2020-01-06 11:02:57 +01:00 committed by Franck Nijhof
parent b701713cfd
commit fa4e1e9c4d
2 changed files with 8 additions and 8 deletions

View File

@ -42,15 +42,15 @@ That's it. You should no be able to use the Google Voice assistant.
{% configuration %} {% configuration %}
client_secrets: client_secrets:
description: The file downloaded from the [Google Actions Console][GActionsConsole], you can redownload them under the "Develop - Device registration" tab. By default the add-on look in the "hassio/share" folder. description: The file downloaded from the [Google Actions Console](https://console.actions.google.com/), you can redownload them under the "Develop - Device registration" tab. By default the add-on look in the "hassio/share" folder.
required: true required: true
type: string type: string
project_id: project_id:
description: The project id can be found in your "google_assistant.json" file or under project settings in the [Google Actions Console][GActionsConsole]. description: The project id can be found in your "google_assistant.json" file or under project settings in the [Google Actions Console](https://console.actions.google.com/).
required: true required: true
type: string type: string
model_id: model_id:
description: The model id can also be found under the "Develop - Device registration tab" in the [Google Actions Console][GActionsConsole]. description: The model id can also be found under the "Develop - Device registration tab" in the [Google Actions Console](https://console.actions.google.com/).
required: true required: true
type: string type: string
{% endconfiguration %} {% endconfiguration %}

View File

@ -51,7 +51,7 @@ entity_id:
title: title:
description: > description: >
A title to be used for the notification if the notifier supports it A title to be used for the notification if the notifier supports it
with [template][template] support. with [template](/docs/configuration/templating/) support.
required: false required: false
type: template type: template
state: state:
@ -80,13 +80,13 @@ skip_first:
message: message:
description: > description: >
A message to be sent after an alert transitions from `off` to `on` A message to be sent after an alert transitions from `off` to `on`
with [template][template] support. with [template](/docs/configuration/templating/) support.
required: false required: false
type: template type: template
done_message: done_message:
description: > description: >
A message sent after an alert transitions from `on` to `off` with A message sent after an alert transitions from `on` to `off` with
[template][template] support. Is only sent if an alert notification [template](/docs/configuration/templating/) support. Is only sent if an alert notification
was sent for transitioning from `off` to `on`. was sent for transitioning from `off` to `on`.
required: false required: false
type: template type: template
@ -205,7 +205,7 @@ sent at 2:15, 2:45, 3:45, 4:45, etc., continuing every 60 minutes.
### Message Templates ### Message Templates
It may be desirable to have the alert notifications include information It may be desirable to have the alert notifications include information
about the state of the entity. [Templates](/docs/configuration/templating/) about the state of the entity. [Templates][template]
can be used in the message or name of the alert to make it more relevant. can be used in the message or name of the alert to make it more relevant.
The following will show for a plant how to include the problem `attribute` The following will show for a plant how to include the problem `attribute`
of the entity. of the entity.