-
Notifications
You must be signed in to change notification settings - Fork 0
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
Various updates on grammar rules and test cases #11
Conversation
1426bf2
to
ba8086b
Compare
Changes related to it have been reverted. |
Add more Python keywords for highlighting; |
993c5a3
to
cdaf147
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A few questions
cdaf147
to
75438c2
Compare
Repushed the changes on |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Would the git history look better by squashing some of the revert/updates you made?
We have the option to squash all the commits when this PR is merged. But I reset the commits, it should look better now. |
1. Use boundary anchor 2. Add python keywords
b0a8115
to
50311f0
Compare
1. Replace hard-coded operators with.*
to match all function and variable names regardless of what comes after the:
since we don't care about them for now.2. Make sure the names following a:
won't be seen as references to a declared object.3. Use the injection approach to apply necessary grammar rules for bitbake conf files4. Implement a minimum set of rules including variables, variable expansion, some keywords etc to reduce conflicts with non-bitbake .conf filesChanges related to what is above have been reverted. This PR is now for grammar rule changes in
bitbake.tmLanguage.json
and test cases