Pros: simplified sintax avoiding ${...}
Const: lack of homogenity compared with httpCustom.ngsi in subscriptions
We have REST-style query ops (GET /v2/entities or GET /v2/entities/{id}) but it would be more complicated defining virtualAttrs on them (they don't use payload in the request).
Is your feature request related to a problem / use case? Please describe.
Use JEXL in queries so an expression can be evaluated on the query results to define virtual attributes.
Describe the solution you'd like
Let's consider an operation like this:
So assuming we have the following entities:
The response to that operation is:
Describe alternatives you've considered
Alternative syntax:
Pros: simplified sintax avoiding
${...}
Const: lack of homogenity compared withhttpCustom.ngsi
in subscriptionsWe have REST-style query ops (
GET /v2/entities
orGET /v2/entities/{id}
) but it would be more complicated definingvirtualAttrs
on them (they don't use payload in the request).Describe why you need this feature