Evaluate adding getDisplayName to IUasDatalinkValue about jmisb HOT 3 CLOSED

Looks like it'll be fine. The tests and other minor cleanups are pretty extensive, but not complicated. I'll finish that up soon.

from jmisb.

Problem is what to do about things like UasDatalinkString that are re-used between tags? If every tag had its own type this would be straightforward, but I'm not sure that feels right.

from jmisb.

The rough plan is an (optional?) constructor argument that initialises in a new private final String field - it'll be easy to fill in at the Factory level, and generally OK elsewhere - you probably know what the String is for when you're making it.

Thoughts on optional?

I liked the idea of different types for different tags because it makes it easier to debug when its a List, and its not much effort to implement because you just subclass and the IDE fills in the constructors - really more test and documentation.

However this is probably enough for UasDatalinkString usages.

from jmisb.