Skip to content

Don't parse CC output for swg.js warnings -- just fix them#18589

Merged
dreamofabear merged 2 commits intoampproject:masterfrom
dreamofabear:fix-master-again
Oct 8, 2018
Merged

Don't parse CC output for swg.js warnings -- just fix them#18589
dreamofabear merged 2 commits intoampproject:masterfrom
dreamofabear:fix-master-again

Conversation

@dreamofabear
Copy link
Copy Markdown

@dreamofabear dreamofabear commented Oct 8, 2018

Update: Don't parse CC output for warnings in swg.js. It doesn't work because CC actually terminates on moduleLoad "warnings", and doesn't generate a compiled JS binary. 🤷‍♂️

I manually replaced all relative paths in type annotations with * in swg.js in one search/replace with regex (!|\?)\.[^>)}]*. I also verified that amp-subscriptions-google extension builds again and this should unbreak master.

I'll chat with the SWG folks on whether we should automate this or wait for a proper fix in #18586.

@dreamofabear dreamofabear changed the title Fix another regex mismatch in compile.js (sorry) Don't parse CC output for swg.js warnings -- just fix them Oct 8, 2018
@dreamofabear dreamofabear merged commit 8ac89ae into ampproject:master Oct 8, 2018
@dreamofabear dreamofabear deleted the fix-master-again branch October 8, 2018 14:45
noranazmy pushed a commit to noranazmy/amphtml that referenced this pull request Oct 18, 2018
…t#18589)

* The 'xx.x% typed' message sometimes doesn't appear.

* Revert CC output parsing and instead replace bogus types in swg.js with *.
Enriqe pushed a commit to Enriqe/amphtml that referenced this pull request Nov 28, 2018
…t#18589)

* The 'xx.x% typed' message sometimes doesn't appear.

* Revert CC output parsing and instead replace bogus types in swg.js with *.
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.

4 participants