Fixes bug where #99, where in path parameters of pipelined requests, $n doesn't necessarily have to have a reachable path. This is helpful in cases when the response of a request on which the current request is dependent on, doesn't return a JSON object but just empty strings

[adisingh007]

Closes #99

Modified the internals.requestRegex.

Now it also matches for a path parameter without any reachable content.

That is, if the payload is:

"requests": [
    { 
        "method": "get",
        "path": "/some/path"
    },
    {
        "method": "get",
        "path": "/another/path/$0"
    }
]

And if the 0th request returns just a string, say, someString,

The path in the 1st request is taken as /another/path/someString

Now the regex has 4 groups:

For example, the URL path is: /some/path/$1.name.firstname/$1.id/$0/something, the matches from (regex101[regex101.com]) is:

Full match: `/some`
p1: N/A
p2: N/A
p3: "some"
  
Full match: `/path`
p1: N/A
p2: N/A
p3: "path"
  
Full match: "/$1.name.firstname"
p1: "1"
p2: "."
p3: "name.firstname"
  
Full match: "/$1.id"
p1: "1"
p2: "."
p3: "id"     
  
Full match: "/$0"
p1: "0"
p2: N/A
p3: ""    
  
Full match: `/something`
p1: N/A
p2: N/A
p3: "something"

[cadecairos]

This looks great, can you rebase it now that the fix in
#98 has been merged?

[adisingh007]

@cadecairos Sure thing. Done. Ready to be merged. Regards, Aditya Singh

…

On Mon, Sep 17, 2018 at 6:30 AM Christopher DeCairos < ***@***.***> wrote: ***@***.**** requested changes on this pull request. This looks great, can you rebase it now that the fix in #98 <#98> has been merged? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#100 (review)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AHHRvEyf7F68qltuKb4oX8608TvDS4Koks5ubvQdgaJpZM4Wq5ld> .