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

[C++] Check for case insensitive keywords #8420

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

razvanalex
Copy link
Contributor

Adds check against case insensitive keywords. Most languages are not affected by this change.

In PHP, some names such as Bool cannot be used because it is a reserved keyword for the bool data type. Adding the field keywords_casing in the configs enables checking in lowercase of all characters against every keyword. This should be safe as flatbuffers does not allow non-ASCII characters in its grammar.

This feature will be used in future PRs to improve PHP support in flatbuffers.

Copy link

google-cla bot commented Oct 8, 2024

Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

View this failed invocation of the CLA check for more information.

For the most up to date status, view the checks section at the bottom of the pull request.

Most languages are not affected by this change. In PHP, some names such
as Bool cannot be used because it is a reserved keyword for to the bool
data type. The field `keywords_casing` in the configs enables checking
all characters in lowercase against every keyword. This should be safe
as flatbuffers does not allow non-ASCII characters in its grammar.
@razvanalex razvanalex force-pushed the keywords-case-insensitive branch from 397926d to 0aabe43 Compare October 8, 2024 14:27
@razvanalex
Copy link
Contributor Author

Sorry for the CLA notice. I mistakenly used the wrong git account. Rebased and now should be fixed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant