-
Notifications
You must be signed in to change notification settings - Fork 26.3k
refactor(compiler): some small compiler refactorings #43129
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
refactor(compiler): some small compiler refactorings #43129
Conversation
This import is not used in the file, so can be removed.
The compliance tests can check source-map segments against expectations encoded into the expectation files. Previously, the encoding of the expected segment was only delimited by whitespace, but this made it difficult to identify segments that started or ended with whitespace. Now these segment expectations are wrapped in double-quotes which makes it easier to read and understand the expectation files.
This commit removes 9 cycles in the dependency graph of the compiler code.
This function is general purpose and by moving it into the `chars.ts` file along with similar helpers, it can be reused in the lexer, for instance.
This is a simple tidy up commit to move to the more specific `===` comparison operator in the HTML lexer/parser.
… interpolations Such interpolations turned up during internal testing at Google, so this commit adds a test to prevent regressions.
…butes This tests a scenario that was failing in an internal project.
@petebacondarwin FYI presubmits went well + I also verified that there are no changes in the extracted message IDs for the app that was affected previously by #42062. |
Note to Caretaker: since this is a part of the PR that was reverted earlier (due to g3 issues), please sync this PR into g3 as a separate change to minimize the risks and simplify the rollback if needed. |
This import is not used in the file, so can be removed. PR Close #43129
…ts (#43129) The compliance tests can check source-map segments against expectations encoded into the expectation files. Previously, the encoding of the expected segment was only delimited by whitespace, but this made it difficult to identify segments that started or ended with whitespace. Now these segment expectations are wrapped in double-quotes which makes it easier to read and understand the expectation files. PR Close #43129
This commit removes 9 cycles in the dependency graph of the compiler code. PR Close #43129
This is a simple tidy up commit to move to the more specific `===` comparison operator in the HTML lexer/parser. PR Close #43129
…ts (#43129) The compliance tests can check source-map segments against expectations encoded into the expectation files. Previously, the encoding of the expected segment was only delimited by whitespace, but this made it difficult to identify segments that started or ended with whitespace. Now these segment expectations are wrapped in double-quotes which makes it easier to read and understand the expectation files. PR Close #43129
This commit removes 9 cycles in the dependency graph of the compiler code. PR Close #43129
This is a simple tidy up commit to move to the more specific `===` comparison operator in the HTML lexer/parser. PR Close #43129
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
These commits were extracted from the reverted #42062 PR since they do not change any behaviour.
This PR let's us land those commits now, and will make the reworking of #42062 simpler.