|
Remove current localization mechanism?
EBALLOT PROPOSAL: remove existing localization mechanism. See above for rationale. Because we no longer utilize the message.messageId property to drive localization scenarios, certain SARIF properties can be retyped as multiformatMessageString instances.
API IMPACT
In the tool object:
Remove the language property.
In the reportingDescriptor object:
Change the type of the name property from message object to string.
Change the type of the shortDescription property from message object to multiformatMessageString object.
Change the type of the fullDescription property from message object to multiformatMessageString object.
In the exception object:
Change the type of the message property from message object back to string (as once it was).
NOTES
The TC is developing a new proposal for localization that may replace the current mechanism that we propose to remove (due to its obvious flaws).
https://github.com/oasis-tcs/sarif-spec/issues/325
|
