You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I find paragraph 8.1 about Claim Path and especially the part that explains the processing of the path components confusing.
What is not clear to me is the difference between a string path component pointing to a JSON array claim and the same pointer with a null at the end.
I find paragraph 8.1 about Claim Path and especially the part that explains the processing of the path components confusing.
What is not clear to me is the difference between a string path component pointing to a JSON array claim and the same pointer with a
null
at the end.Using the example of paragraph
I would like to ask if the two paths bellow will produce the same results:
["degrees", null]
["degrees"]
To my understanding,
["degrees", null]
) will return a set of two objects (each one representing a degree)["degrees"]
) will return a set containing a Json Array (with the two degrees)Is this the expected outcome or both paths should return just a set of two degrees?
Furthermore, I have the impression that a
path
should always begin with a string simply because it has to be applied in the top-level json objectThe text was updated successfully, but these errors were encountered: