JSON strings are UNICODE yet the OWRT JSON library accepts ASCII

For Developers
1 
	procd_append_param error "Your 1st message here!\x0b"
	procd_append_param error "Your 2nd message here!\x0b"

should not be accepted (but they are) -

root@pWPW10-1:~# json_get_values _a "errors"
root@pWPW10-1:~# echo -e $_a
Your 1st message here!
                       Your 2nd message here!

root@pWPW10-1:~# echo $_a
Your 1st message here!\x0b Your 2nd message here!\x0b
root@pWPW10-1:~# ubus -v call service list '{"name": "blah", "verbose": true}'
{
        "blah": {
                "instances": {
                        "instance1": {
                                "running": false,
                                "term_timeout": 5,
                                "exit_code": 0,
                                "errors": [
                                        "Your 1st message here!\\x0b",
                                        "Your 2nd message here!\\x0b"
                                ]
                        }
                },
                "triggers": [

                ]
        }
}
root@pWPW10-1:~#

Is this the expected behaviour?

N.B. - coding the UNICODE equivalent, \u000b (which echo does not 'recognise'), is also accepted

2

More curiosities (although as expected).
Hardcoding a VT character in the init script, it is interpreted as text UNICODE (but where?) -

root@pWPW10-1:~# ubus -v call service list '{"name": "blah", "verbose": true}'
{
        "blah": {
                "instances": {
                        "instance1": {
                                "running": false,
                                "term_timeout": 5,
                                "exit_code": 0,
                                "errors": [
                                        "Your 1st message here!\u000b",
                                        "Your 2nd message here!\u000b"
                                ]
                        }
                },
                "triggers": [

                ]
        }
}
root@pWPW10-1:~#
3

Hmm. No developers reading this forum?

4

Create a bug report over at GitHub instead?