PQL looks like a cracked out parrot ran across my keyboard: /? query= posts( ids: [1, 1499, 1178], order: $order )@posts.

PQL looks like a cracked out parrot ran across my keyboard: /? query= posts( ids: [1, 1499, 1178], order: $order )@posts. id| date(format: d/m/Y)| title< skip(if: false) >| --props& order=title|ASC& props= url| author. name| url All-in-all this seems like a very roundabout way to achieve HTTP-level caching for queries. Reasoning about the query as a literal string instead of _data_ is where I think this went off the rails. I probably would have just added middleware to allow for base64 encoded queries and then gone that route. A query can get deterministically hashed into a string of chars.