-
Notifications
You must be signed in to change notification settings - Fork 3.9k
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
🚀 Separating BaseTemplate from template-impl. #30208
Conversation
This pull request introduces 3 alerts when merging dfe37a4 into 767775f - view on LGTM.com new alerts:
|
This pull request introduces 1 alert when merging 9658906 into 767775f - view on LGTM.com new alerts:
|
Not sure about this approach. Wouldn't it be a lot easier to:
If we do so, we can keep all code and APIs intact. This will end up just a very simple change. |
Can we move |
There are a few extensions that use |
Hey @dvoytenko , could you clarify point 2 in the PR? I am currently running into a type error in which I am instantiating an abstract class - this did not happen when |
Pinging @ampproject/build-cop again for flaky test. |
Could you provide more information on the flaky test? We currently have #30247 to deflake one of the test, but not sure that's the one which is blocking you. |
Based on the most recent cross-browser test, the test that failed was indeed a handshake test. |
Sweet:
|
* initial attempt * correction * undo * fix lgtm issue * first attempt in moving template * moved BaseTemplate to its own class * missing changes * uncomment existing test * license header * import * comment out test * lint * type error * undo abstract * workaround * lint * typeof change * conflict * abs fix Co-authored-by: Derek Tse <derektse@google.com>
As @dvoytenko has pointed,
BaseTemplate
fromservice/template-impl.js
could be refactored to reduce its size. This will be achieved by separatingBaseTemplate
.