Example:

Update of Authoritative nameserver(idnssoamname) raises warning message:

    semantic of '--name-server' option was changed: the option is used
    only for setting up the SOA MNAME attribute.

    To edit NS record(s) in zone apex, use command 'dnsrecord-mod [zone]
    @ --ns-rec=nameserver'

This message is defined in API. It's a valid message for CLI. But for Web UI users the CLI commands may be irrelevant.

Web UI should use different message.

Web UI receives:

{
    "code": 13005, 
    "message": "semantic of '--name-server' option was changed: the option is used only for setting up the SOA MNAME attribute.\nTo edit NS record(s) in zone apex, use command 'dnsrecord-mod [zone] @ --ns-rec=nameserver'.", 
    "name": "OptionSemanticChangedWarning", 
    "type": "warning"
}

From this information it's difficult for Web UI to deterministically distinguish it from other OptionSemanticChangedWarning warnings since {{{message}}} part does not have to be in English language and the order of options could be change by translation.

Ideally API should sent a unique warning message identifier(code?) so clients could show relevant client-specific message.