Hi,
> Could you write a little bit about the underlying cause of this just
> so I can understand better?
it is basically mimicking JavaScript object access syntax where labels after a
dot must be valid identifiers.
In JS, an expression `obj.foo-bar.baz` would be interpreted as `obj.foo` minus
Thanks. That works.
Could you write a little bit about the underlying cause of this just
so I can understand better?
On Wed, Aug 12, 2020 at 3:59 PM Jo-Philipp Wich wrote:
>
> Hi,
>
> as already implied by Dirk, you need to use bracket notation for labels that
> are not valid variable
Hi,
as already implied by Dirk, you need to use bracket notation for labels that
are not valid variable identifiers.
So instead of `@.foo-bar` use `@["foo-bar"]`.
~ Jo
signature.asc
Description: OpenPGP digital signature
___
openwrt-devel mailing
On Wed, 2020-08-12 at 14:20 -0500, Michael Jones wrote:
> Hi List,
>
> I am trying to query netifd via ubus for the list of ipv4 ipaddresses
> associated with an interface.
>
> Currently my query looks like
>
> ubus call network.interface.wan status | jsonfilter -e "@.ipv4-
> address"
> Syntax
Hi List,
I am trying to query netifd via ubus for the list of ipv4 ipaddresses
associated with an interface.
Currently my query looks like
ubus call network.interface.wan status | jsonfilter -e "@.ipv4-address"
Syntax error: Invalid escape sequence
In expression @.ipv4-address
Near here