fix(046_05_01): a Subscription's q in a JSON body is not URL-encoded

Ken Zangelinrequested to merge
fix/subscription-q-not-url-encoded into develop

The q member of a Subscription is a JSON string (TS 104-175 clause 5.2.6.5.2). Percent-encoding belongs to a q in a URL query string, not to one in a body.

name=="Eiffel%20Tower" in the Subscription asks for a name with a literal %20 in it, which the Building does not have, so no notification is sent. name=="Eiffel Tower" is what the TC means.

1 Test Case, one line in data/subscriptions/subscription-building-entities-active-watchedAttributes-query.jsonld (only 046_05 uses it). It fails on develop and passes with this MR.

Merge request reports

data/subscriptions/subscription-building-entities-active-watchedAttributes-query.jsonld

+1 −1
Changes for data/subscriptions/subscription-building-entities-active-watchedAttributes-query.jsonld: 1 added line, 1 removed line.
Original line number Diff line number Diff line
@@ -3,7 +3,7 @@ 
   "type":"Subscription",

   "isActive": true,

   "watchedAttributes": ["airQualityLevel"],

   "q": "name==\"Eiffel%20Tower\"",

   "q": "name==\"Eiffel Tower\"",

   "entities":[

      {

         "type":"Building"