On Apr 24, 2024, at 3:22 PM, Erik Wienhold wrote:
> Thanks Peter! But what is the definition of the entire path expression?
> Perhaps something like:
>
> ::= { "." }
>
> That would imply that "$.$foo" is a valid path that accesses a variable
> member (but I guess the path evaluation is a
On 2024-04-24 13:52 +0200, David E. Wheeler wrote:
> On Apr 24, 2024, at 05:51, Peter Eisentraut wrote:
>
> >A is classified as follows.
> >
> >Case:
> >
> >a) A that is a is a > path context variable>.
> >
> >b) A that begins with is a
> > .
> >
> >c) Ot
On Apr 24, 2024, at 05:46, Peter Eisentraut wrote:
> I have committed this patch, and backpatched it, as a bug fix, because the
> existing description was wrong. To keep the patch minimal for backpatching,
> I didn't do the conversion to a list. I'm not sure I like that anyway,
> because it
On Apr 24, 2024, at 05:51, Peter Eisentraut wrote:
>A is classified as follows.
>
>Case:
>
>a) A that is a is acontext variable>.
>
>b) A that begins with is a
> .
>
>c) Otherwise, a is a .
>
> Does this help? I wasn't following all the discussion to
On 18.03.24 01:09, Erik Wienhold wrote:
The error message 'syntax error at or near "$oo" of jsonpath input' for
the second case ($.f$oo), however, looks as if the scanner identifies
'$oo' as a variable instead of contiuing the scan of identifier (f$oo)
for the member accessor. Looks like a bug t
On 17.03.24 20:12, Erik Wienhold wrote:
Mentioning JSON and \v in the same sentence is wrong: JavaScript allows
that escape in strings but JSON doesn't. I think the easiest is to just
replace "JSON" with "JavaScript" in that sentence to make it right. The
paragraph also already says "embedded s
On Mar 17, 2024, at 20:09, Erik Wienhold wrote:
>
> On 2024-03-17 20:50 +0100, David E. Wheeler wrote:
>> On Mar 17, 2024, at 15:12, Erik Wienhold wrote:
>>> So I think it makes sense to reword the entire backslash part of the
>>> paragraph and remove references to JSON entirely. The attached p
On 2024-03-17 20:50 +0100, David E. Wheeler wrote:
> On Mar 17, 2024, at 15:12, Erik Wienhold wrote:
> > So I think it makes sense to reword the entire backslash part of the
> > paragraph and remove references to JSON entirely. The attached patch
> > does that and also formats the backslash escap
On Mar 17, 2024, at 15:12, Erik Wienhold wrote:
> Hi David,
Hey Erik. Thanks for the detailed reply and patch!
> So I think it makes sense to reword the entire backslash part of the
> paragraph and remove references to JSON entirely. The attached patch
> does that and also formats the backslas
Hi David,
On 2024-03-16 19:39 +0100, David E. Wheeler wrote:
> The jsonpath doc[1] has an excellent description of the format of
> strings, but for unquoted path keys, it simply says:
>
> > Member accessor that returns an object member with the specified
> > key. If the key name matches some name
On Mar 16, 2024, at 14:39, David E. Wheeler wrote:
> I went looking for the JavaScript rules for an identifier and found this in
> the MDN docs[2]:
>
>> In JavaScript, identifiers can contain Unicode letters, $, _, and digits
>> (0-9), but may not start with a digit. An identifier differs from
Hackers,
The jsonpath doc[1] has an excellent description of the format of strings, but
for unquoted path keys, it simply says:
> Member accessor that returns an object member with the specified key. If the
> key name matches some named variable starting with $ or does not meet the
> JavaScrip
12 matches
Mail list logo
