Skip Menu |

This queue is for tickets about the JSON-Path CPAN distribution.

Report information
The Basics
Id: 122529
Status: resolved
Priority: 0/
Queue: JSON-Path
People
Owner: Nobody in particular
Requestors: baldmantom [...] gmail.com
Cc:
AdminCc:
Bug Information
Severity: (no value)
Broken in: (no value)
Fixed in: (no value)

History Show all quoted text
  Tue Jul 18 10:36:54 2017 baldmantom [...] gmail.com - Ticket created
Subject: paths() does not match if path to find contains multiple recursive descents
Date: Tue, 18 Jul 2017 10:36:46 -0400
To: bug-JSON-Path [...] rt.cpan.org
From: Thomas Helsel <baldmantom [...] gmail.com>
Hello. Thanks for your quick turnaround of the previous issues I reported. In the latest version (0.400), I discovered something new. If a path to find contains multiple recursive descents (e.g. $..foo..value), paths() doesn't seem to return any results. I've attached a test script which shows the issue.

Message body is not shown because sender requested not to inline it.

  Tue Jul 18 10:51:00 2017 popefelix [...] gmail.com - Correspondence added
On Tue Jul 18 10:36:54 2017, baldmantom wrote: Show quoted text
> Hello. Thanks for your quick turnaround of the previous issues I reported. > In the latest version (0.400), I discovered something new. If a path to > find contains multiple recursive descents (e.g. $..foo..value), paths() > doesn't seem to return any results. I've attached a test script which shows > the issue.
I confirm this bug.
  Tue Jul 18 10:51:00 2017 The RT System itself - Status changed from 'new' to 'open'
  Thu Jul 27 16:39:34 2017 popefelix [...] gmail.com - Correspondence added
On Tue Jul 18 10:51:00 2017, popefelix wrote: Show quoted text
> On Tue Jul 18 10:36:54 2017, baldmantom wrote:
> > Hello. Thanks for your quick turnaround of the previous issues I > > reported. > > In the latest version (0.400), I discovered something new. If a path > > to > > find contains multiple recursive descents (e.g. $..foo..value), > > paths() > > doesn't seem to return any results. I've attached a test script which > > shows > > the issue.
> > I confirm this bug.
This is fixed in 0.411
  Thu Jul 27 16:39:52 2017 popefelix [...] gmail.com - Correspondence added
On Thu Jul 27 16:39:34 2017, popefelix wrote: Show quoted text
> On Tue Jul 18 10:51:00 2017, popefelix wrote:
> > On Tue Jul 18 10:36:54 2017, baldmantom wrote:
> > > Hello. Thanks for your quick turnaround of the previous issues I > > > reported. > > > In the latest version (0.400), I discovered something new. If a path > > > to > > > find contains multiple recursive descents (e.g. $..foo..value), > > > paths() > > > doesn't seem to return any results. I've attached a test script which > > > shows > > > the issue.
> > > > I confirm this bug.
> > This is fixed in 0.411
  Thu Jul 27 16:39:58 2017 popefelix [...] gmail.com - Status changed from 'open' to 'resolved'
  Thu Jul 27 16:39:58 2017 popefelix [...] gmail.com - Correspondence added
On Thu Jul 27 16:39:34 2017, popefelix wrote: Show quoted text
> On Tue Jul 18 10:51:00 2017, popefelix wrote:
> > On Tue Jul 18 10:36:54 2017, baldmantom wrote:
> > > Hello. Thanks for your quick turnaround of the previous issues I > > > reported. > > > In the latest version (0.400), I discovered something new. If a path > > > to > > > find contains multiple recursive descents (e.g. $..foo..value), > > > paths() > > > doesn't seem to return any results. I've attached a test script which > > > shows > > > the issue.
> > > > I confirm this bug.
> > This is fixed in 0.411