Re: Shouldn't jsonpath .string() Unwrap?

David E. Wheeler <david@justatheory.com>

From: "David E. Wheeler" <david@justatheory.com>

To: Chapman Flack <jcflack@acm.org>

Cc: Andrew Dunstan <andrew@dunslane.net>, "David G. Johnston" <david.g.johnston@gmail.com>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>, Jeevan Chalke <jeevan.chalke@enterprisedb.com>

Date: 2024-06-14T16:03:54Z

Lists: pgsql-hackers

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

Teach jsonpath string() to unwrap in lax mode
- 653d3969bb01 17.0 landed

Attachments

v2-0001-Teach-jsonpath-string-to-unwrap-in-lax-mode.patch (application/octet-stream) patch v2-0001
(unnamed) (text/plain)

> On Jun 14, 2024, at 11:25, Chapman Flack <jcflack@acm.org> wrote:
> 
> I would s/extepsions/exceptions/ in the added documentation. :)

Bah, fixed and attached, thanks.

> Offhand (as GitHub PRs aren't really The PG Way), if they were The Way,
> I would find this one a little hard to follow, being based at a point
> 28 unrelated commits ahead of the ref it's opened against. I suspect
> 'master' on theory/postgres could be fast-forwarded to f1affb6 and then
> the PR would look much more approachable.

Yeah, I pushed the PR and branch before I synced master, and GitHub was taking a while to notice and update the PR. I fixed it with `git commit --all --amend --date now --reedit-message HEAD` and force-pushed (then fixed the typo and fixed again).

D