Skip to main content

SignalVisibilityController

Purpose

A controller that responds to SignalInputController notifications. This controller can hide or show its content based on the expression given in showValue, which it will use to evaluate the value of the input. based on changes to inputs and their values.

This controller can be anywhere in the DOM tree and it will receive notifications from any SignalInputController with the same nameValue as the nameValue of this controller.

Actions

ActionPurpose
--

Targets

TargetPurposeDefault
---

Classes

ClassPurposeDefault
hideThe class used to hide the content of the element when the showValue expression evaluates to falsehide

Values

ValueTypeDescriptionDefault
nameStringThe name of the input value whose value to react to. This name should be the same as the nameValue of the SignalInputController you want to sync with.-
showStringA simple expression which will be evaluated against the value received from SignalInputController. If the expression evaluates to true, the hideClass is removed from the element. If the expression evaluates to false, the hideClass is added to the element.-

Expressions follow the syntax of [operator][value] e.g. <3 or >=3 and can be combined with && and || operators.

Example expressions that can be used:

ExpressionExplanation
defaultwill be shown when the value is empty
>0
>= 50 && <100
==red
!=black and yellowEverything that is not an operator is treated as a value. This is evaluated as inputValue != "black and yellow"
==23 || ==25

Supported operators:

Operator
default
evaluates to true when value is empty, e.g. ""
==
&&
||
>
>=
<
<=

Note: Only simple expressions are supported. Logical groupings e.g. (a || b) && c are not supported.
Variable bindings e.g. <=a are not supported.
You can only use only one type of logical concatenation at a time. i.e. >3 && ==5 && <10, or >3 || ==5 || <10. Expressions that mix the two, i.e. >3 || ==2 && <10 are not supported.

Security Note: This controller is designed to be safe. It does not violate any strong CSP policies, and it does NOT use eval(). The expressions are parsed as strings and predicate functions are created based on the presence or absence of recognised operators in the string, and the values that the SignalInputController broadcasts from the user are tested against the expression using built-in JavaScript operators for each math operation.

Events

EventWhenDispatched onevent.detail
signal:visibility:${nameValue}:showWhen a signalled value matches the predicate expression and this element is shownThe controller root element
elementthe controller root element
predicatethe expression the controller used to try and match the value
valuethe value that was received
signal:visibility:${nameValue}:hideWhen a signalled value fails the predicate expression and this element is hiddenThe controller root element
elementthe controller root element
predicatethe expression the controller used to try and match the value
valuethe value that was received

Side Effects

None

How to Use