It can happen that properties of certain types return null for the getValue, but not for the getTypedValue and the other way around.
Example 1: getValue() == null and getTypedValue() != null
for all properties that have a value that is not backed by a string representation (for instance selection properties)
Example 2: getValue() != null and getTypedValue() == null
for all properties where the value cannot be parsed into the correct type. For instance an integer that has a string representation that is greater than MAX_INT.
Ideally both methods should return null or both should return not-null.
I am pausing this issue since changes to the semantics of these functions are inherently risky (given the lack of proper regression tests in the code base).
It can happen that properties of certain types return null for the getValue, but not for the getTypedValue and the other way around.
Example 1: getValue() == null and getTypedValue() != null for all properties that have a value that is not backed by a string representation (for instance selection properties)
Example 2: getValue() != null and getTypedValue() == null for all properties where the value cannot be parsed into the correct type. For instance an integer that has a string representation that is greater than MAX_INT.
Ideally both methods should return null or both should return not-null.