bug report: query field in JSON output is not semantic

bug report: query field in JSON output is not semantic

[Martin Monperrus]

Hi Notmuch team,

### Action:
$ notmuch search --output=summary --format=json "bug"'
{
   "thread": "000000000002a9f9",
   "timestamp": 1634505852,
   "date_relative": "2021-10-17",
   "matched": 6,
   "total": 14,
   "authors": "Martin Monperrus, Long Zhang| Benoit Baudry",
   "subject": "ChaosETH related work",
   "query": [
     "id:297c63e4490f35f52872c047216dc7239ab066a9.camel@csc.kth.se 
id:01e9953643a1b790370745247cd8530c302e8452.camel@csc.kth.se 
id:039b5a163a3ddd460b8b382051fc38f2aea7780e.camel@csc.kth.se 
id:042f2a8e038543f488232f681cfd902f@kth.se id:e7e3771ad783cbbb9b4efe18da12f0409b18d95d.camel@kth.se 
id:cd5d56e2789242e0a67cb26a77818638@kth.se",
     "id:fe72077bb44e478284eeaee78b815e92@kth.se 
id:81252c3aed01c60911297bda5e89fa50eef8d776.camel@csc.kth.se 
id:a82bbff022878f1273a4c2abb3ef784ce9803755.camel@csc.kth.se 
id:f2509185a4ef492388182306a317c382@kth.se id:69116b70151c4d24a9429951e2e8b647@kth.se 
id:a67c09ed-b56d-63de-beb8-fc59c438228e@kth.se 
id:f047bb2cf746526025ed67ffdfd675570c6f5579.camel@csc.kth.se 
id:c68abd54ce443ad6992269e97d142d45547ae176.camel@csc.kth.se"
   ],
   "tags": [
     "replied"
   ]
}

###Expected behavior:
"query" field contains a semantic list of ids that can be manipulated in pure JSON

### Actual behavior:
"query" field contains a string that has to be parsed, split by space




\r

Re: bug report: query field in JSON output is not semantic

[David Bremner]

Martin Monperrus <martin.monperrus@gnieh.org> writes:

> Hi Notmuch team,
>

Hi Martin.

>
> ###Expected behavior:
> "query" field contains a semantic list of ids that can be manipulated in pure JSON
>

This might indeed have been a reasonable design, but it's not what is
documented in devel/schemata. So it depends which expectations I guess.

> ### Actual behavior:
> "query" field contains a string that has to be
> parsed, split by space

Currently we do not fix the query in question to be a list of
id's, so I guess it would conform to the current spec to outpu
t some
other kind of query that needed to be parsed. I don't forsee doing that,
though, so perhaps in the long term we can make this change.

It would require potentially adjusting the emacs front end and any other
client relying on the JSON format, so it's not a completely trivial
change.

Thanks for your suggestion,

David