Community
Participate
Working Groups
Errors and warnings can be created for a structural feature of an object. However, it may be helpful to assign a certain range of the feature value to the validation result, e.g. a very long string may be invalid due to some unmatched regex. Clients should be able to set the offset / length of the error / warning.
This is interesting for ValueConverterExceptions, too.
This is a pre-req to validate whitespace consistency in Xtend2's rich strings.
Done. I'll file a second ticket for the value converter exceptions.
Closing all bugs that were set to RESOLVED before Neon.0