-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
[CALCITE-4238] Create a default parser configuration, to reduce redundant information in sub-parsers #2167
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Is the appveyor error relevant? Or is it a spurious error? |
julianhyde
added a commit
to julianhyde/calcite
that referenced
this pull request
Sep 28, 2020
…list of non-reserved keywords Note that "HOP" and "TUMBLE" had been added to core/main's nonReservedKeywords but not core/test, server, babel; that was probably a mistake. Close apache#2167
julianhyde
force-pushed
the
4238-common-keywords
branch
from
September 28, 2020 18:06
a137eda
to
16ef259
Compare
julianhyde
added a commit
to julianhyde/calcite
that referenced
this pull request
Sep 28, 2020
…dant information in sub-parsers With this change, we no longer require each sub-project parser to have its own list of non-reserved keywords. For example, "HOP" and "TUMBLE" had been added to core/main's nonReservedKeywords but not core/test, server, babel; that was probably a mistake. Create default_config.fmpp, include it in derived parsers, and remove properties from parsers' config.fmpp files if they are the same as those in default_config.fmpp. Close apache#2167
julianhyde
added a commit
to julianhyde/calcite
that referenced
this pull request
Sep 28, 2020
…dant information in sub-parsers With this change, we no longer require each sub-project parser to have its own list of non-reserved keywords. For example, "HOP" and "TUMBLE" had been added to core/main's nonReservedKeywords but not core/test, server, babel; that was probably a mistake. Create default_config.fmpp, include it in derived parsers, and remove properties from parsers' config.fmpp files if they are the same as those in default_config.fmpp. Close apache#2167
julianhyde
force-pushed
the
4238-common-keywords
branch
from
September 29, 2020 06:45
16ef259
to
9b5018d
Compare
…dant information in sub-parsers With this change, we no longer require each sub-project parser to have its own list of non-reserved keywords. For example, "HOP" and "TUMBLE" had been added to core/main's nonReservedKeywords but not core/test, server, babel; that was probably a mistake. Create default_config.fmpp, include it in derived parsers, and remove properties from parsers' config.fmpp files if they are the same as those in default_config.fmpp. Close apache#2167
julianhyde
force-pushed
the
4238-common-keywords
branch
from
September 29, 2020 19:42
9b5018d
to
0b2dfb7
Compare
MalteBellmann
pushed a commit
to caespes/calcite
that referenced
this pull request
Feb 21, 2021
…dant information in sub-parsers With this change, we no longer require each sub-project parser to have its own list of non-reserved keywords. For example, "HOP" and "TUMBLE" had been added to core/main's nonReservedKeywords but not core/test, server, babel; that was probably a mistake. Create default_config.fmpp, include it in derived parsers, and remove properties from parsers' config.fmpp files if they are the same as those in default_config.fmpp. Close apache#2167
jamesstarr
pushed a commit
to jamesstarr/calcite
that referenced
this pull request
Jun 18, 2021
…dant information in sub-parsers With this change, we no longer require each sub-project parser to have its own list of non-reserved keywords. For example, "HOP" and "TUMBLE" had been added to core/main's nonReservedKeywords but not core/test, server, babel; that was probably a mistake. Create default_config.fmpp, include it in derived parsers, and remove properties from parsers' config.fmpp files if they are the same as those in default_config.fmpp. Close apache#2167
jamesstarr
pushed a commit
to jamesstarr/calcite
that referenced
this pull request
Jun 18, 2021
…dant information in sub-parsers With this change, we no longer require each sub-project parser to have its own list of non-reserved keywords. For example, "HOP" and "TUMBLE" had been added to core/main's nonReservedKeywords but not core/test, server, babel; that was probably a mistake. Create default_config.fmpp, include it in derived parsers, and remove properties from parsers' config.fmpp files if they are the same as those in default_config.fmpp. Close apache#2167 Change-Id: I6f2f6360c34a7d273f503c699c9924dfb31ecf0f
9 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.