Open nkylstad opened 8 months ago
@altinnadmin kan du gi meg tilgang til denne tavla, så jeg kan jobbe med denne saken?
@nkylstad jeg trenger en kort forklaring på denne før jeg kan forslå tekster.
@nkylstad hva er status på denne? jeg har mistet litt oversikten etter ferien.
@Annikenkbrathen vet du status på denne? Er det noe jeg kan ta inn i neste sprint tror du?
Description
A lot of properties can now be defined as either a static value or as an expression. F.ex:
These can now be set as true/false in our config view, but they can also be configured as an expression. If a boolean/expression value is set as an expression, the config will be disabled in the config panel, and inform the user in the help text
In addition, we currently only support boolean/expression type values. We should support all property types that can be either a static value or expression (string, number, etc).
When the user configures a component for the first time, should they be given a choice when it comes to this type of component? Or a link that takes them to the expression editor for that property? Should we integrate the expression editor directly with the property?