Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Clarify wrapping filter expressions in parentheses #499

Merged
merged 3 commits into from
Aug 9, 2023
Merged

Conversation

glyn
Copy link
Collaborator

@glyn glyn commented Aug 8, 2023

Make it clear that this is not required, unlike in the original JSONPath article. Also, avoid using such parentheses in examples for consistency.

@glyn glyn requested a review from cabo August 8, 2023 18:52
Make it clear that this is not required, unlike in the original JSONPath
article. Also, avoid using such parentheses in examples for consistency.
@@ -1173,6 +1173,11 @@ They have the normal semantics of Boolean algebra and obey its laws
(see, for example, {{BOOLEAN-LAWS}}).
Parentheses MAY be used within `logical-expr` for grouping.

It is not required that `logical-expr` consist of
a parenthesized expression (which was required in {{JSONPath-orig}}),
although it can be and the semantics are the same
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

comma after "be"?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, I think that works well. Added.

@@ -1173,6 +1173,11 @@ They have the normal semantics of Boolean algebra and obey its laws
(see, for example, {{BOOLEAN-LAWS}}).
Parentheses MAY be used within `logical-expr` for grouping.

It is not required that `logical-expr` consist of
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We now have removed all examples that actually show what is discussed here?
(We know what it is, but readers may not.)

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, I was a little concerned about that too, so I've added a specific example near the top of the filter example table.

@glyn glyn merged commit 52448f4 into main Aug 9, 2023
2 checks passed
@glyn glyn deleted the filter-parens branch August 9, 2023 00:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants