Update Main UI expressions docs #2111
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The docs mention chart pages as an exception where expressions aren't supported, but openhab/openhab-webui#1649 introduced support. This updates the docs. Signed-off-by: Florian Hotze <[email protected]>
✅ Thanks for your pull request to the openHAB documentation! The result can be previewed at the URL below (this comment and the preview will be updated if you add more commits).
To edit notification comments on pull requests, go to your Netlify site configuration. |
stefan-hoehn
approved these changes
Aug 4, 2023
|
@florian-h05 still in draft? |
|
Yes. @ghys Can you please have a look at this minor doc change and approve if it's correct? |
ghys
reviewed
Aug 4, 2023
ui/building-pages.md
Outdated
| @@ -144,7 +144,7 @@ See the [Component Reference](./components/) for details about the different lib | |||
|
|
|||
| ## Dynamically Configuring Components with Expressions | |||
|
|
|||
| Virtually everywhere - with the notable exception of chart pages - every time you need a config prop to be dynamically updated, you can use an expression to configure it. | |||
| Virtually everywhere - with the notable exception of config properties of user-created widgets - every time you need a config prop to be dynamically updated, you can use an expression to configure it. | |||
There was a problem hiding this comment.
As I understand it now, this isn't true:
You can insert user-created widgets from another parent component and have their properties configured with expressions:
# Personal widget
uid: widget_4064e9fb1e
tags: []
props:
parameters:
- description: A text prop
label: Prop 1
name: prop1
required: false
type: TEXT
parameterGroups: []
component: f7-card
config:
style:
display: flex
justify-content: center
slots:
default:
- component: oh-link
config:
text: =props.prop1
class:
- margin# Inserting the personal widget and configuring prop1 with an expression
component: widget:widget_4064e9fb1e
config:
prop1: =2+3
There was a problem hiding this comment.
Thanks for the hint!
In the widget editor, properties are not evaluated, openhab/openhab-webui#2007 adds a note about that.
Signed-off-by: Florian Hotze <[email protected]>
|
@stefan-hoehn This is ready to be merged now. |
stefan-hoehn
approved these changes
Aug 7, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The docs mention chart pages as an exception where expressions aren't supported, but openhab/openhab-webui#1649 introduced support. This updates the docs.