The values of the exports object have to resolve to a name and a property of a UiComponent instance, separated by a ':', for example
The export target name has to include the UI component "namespace".
In your example, you set the value to a string, which resolves to a property of the UiComponent that is the export source.
The export is undefined when you inspect it because that is not a valid export target.
Here is an example that works:
The above will copy the value of the
shouldShowMessage property into the property
showMessage of a UiComponent with the full name
foo.bar every time the value changes.
Note that this will not automatically make the target property a KO observable, too. That has to be declared explicitly, if value changes should trigger KO to rerender DOM nodes that access that property.
By the way, adding
shouldShowMessage to the
tracks object will make it a ko-es5 observable automagically. Using a literal
ko.observable() works, too.
In the example above, the
exportTargetProperty are configured in the
defaults. They also could be specified as part of the UiComponent options in the JSON, which usually makes more sense, since that is where the UiComponent hierarchy including the UiComponent names are defined.
Finally, I would like to note that I personally think your solution using a value object to pass the value to the other UI component is better than using exports or imports. In my experience keeping shared state in the DOM or in UiComponents is a recipe for spaghetti OOP in all but the simplest cases.