Docs, properties are passed by value and dependencies by name

In it isn’t super clear that a ux:Dependency should be passed by name. And because this is inconsistent with how ux:Property is passed (which is by value as you would expect) it should probably be more clearly stated than in the the code examples. And perhaps repeated a million times… and maybe even added in the error message when a dependency isn’t passed properly.


Thanks for the feedback.

The article you are linking is about to go away, as we now have a new and shiny full section dedicated to UX Markup in the outline. Please check that out and see if things are more clear over there.

I saw that one earlier, but would be great to add a bullet in the list at the end

• Dependencies are passed by name without curly braces (“myDep”) and not as a value ("{myProp}")