Allow user to invoke query and optQuery ,with a JSONPointer

[dtalex]

It would be good for user's code readability to be able to invoke methods "query" and "optQuery" with a user-provided JSONPointer

[stleary]

Looks reasonable, if nothing comes up in the unit tests, and no objections from @erosb. I will add some tests. Comments need to be cleaned up. For example spelling on line 1365, and param is not a string on line 1380.

[erosb]

I checked this PR yesterday and I have no objections. Thanks.

…

On 27 Feb 2017 04:05, "Sean Leary" ***@***.***> wrote: Looks reasonable, if nothing comes up in the unit tests, and no objections from @erosb <https://github.com/erosb>. I will add some tests. Comments need to be cleaned up. For example spelling on line 1365, and param is not a string on line 1380. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#324 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAQrBuDyR_gFN0xnqmacg-33Iueq0w5dks5rgj2FgaJpZM4MMA7m> .

[stleary]

What problem does this code solve?
This is an enhancement, not a bug fix. API methods using JSONPointer for queries are added as a convenience.

Risks
Very low risk.

Changes to the API?
Yes, new API methods are added:

jsonObject.query(JSONPointer)
jsonObject.optQuery(JSONPointer)
jsonArray.query(JSONPointer)
jsonArray.optQuery(JSONPointer)

Will this require a new release?
No, this change can be rolled into the next release.

Should the documentation be updated?
Not needed.

Does it break the unit tests?
No.

Was any code refactored in this commit?
Yes. The query(String) and optQuery(String) methods were changed to call the new API. This was a reasonable change.
**NOTE: ** There are a few typos in the comments, which should be fixed the next time this code is touched.

Review status
Approved. The usual 3 day review period is skipped, since this pull request has already been up for a month without objection. Will merge in 1 day.