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 boolean literals in specification #1248

Merged
merged 1 commit into from
Dec 7, 2023

Conversation

MaryamTaj
Copy link
Contributor

@MaryamTaj MaryamTaj commented Nov 25, 2023

Fixes #1232

Proposed Changes

Include "TRUE" | "FALSE" when you define boolean literals in the spec.md

Release Note


@MaryamTaj MaryamTaj changed the title Resolves #1232 Clarify boolean literals in specification Nov 25, 2023
cesql/spec.md Outdated
@@ -117,7 +117,7 @@ CESQL defines 3 different literal kinds: integer numbers, `true` or `false` bool
digit ::= [0-9]
number-literal ::= digit+

boolean-literal ::= "true" | "false"
boolean-literal ::= "true" | "false" | "TRUE" | "FALSE"
Copy link
Collaborator

Choose a reason for hiding this comment

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

Is there a format that means "any case", so that TrUe would be acceptable too?

Copy link
Collaborator

Choose a reason for hiding this comment

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

@MaryamTaj I couldn't find a way... can you add a comment to indicate that it's case insensitive?
e.g.

boolean-literal ::= "true" | "false"       (* Case insensitive *)

Copy link
Collaborator

Choose a reason for hiding this comment

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

@MaryamTaj we chatted about this on today's call... are you ok with the above suggestion?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

@duglin Thank you so much for letting me know! I'd be happy to make the changes:)

Copy link
Contributor

Choose a reason for hiding this comment

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

So just to check, this is intended to match True and False (or, less likely, tRUE and fALSE)? I'm pretty sure that's the aim, just checking.

Signed-off-by: MaryamTaj <tajm48822@gmail.com>
@duglin
Copy link
Collaborator

duglin commented Dec 5, 2023

LGTM

@duglin
Copy link
Collaborator

duglin commented Dec 7, 2023

Approved on the 12/7 call

@duglin duglin merged commit d2e6980 into cloudevents:main Dec 7, 2023
2 checks passed
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.

CESQL: clarify TRUE and true, FALSE and false are the same
3 participants