-
Notifications
You must be signed in to change notification settings - Fork 12k
fix(@angular-devkit/build-angular): add missing declaration types … #13421
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
Conversation
We found a Contributor License Agreement for you (the sender of this pull request), but were unable to find agreements for all the commit author(s) or Co-authors. If you authored these, maybe you used a different email address in the git commits than was used to sign the CLA (login here to double check)? If these were authored by someone else, then they will need to sign a CLA as well, and confirm that they're okay with these being contributed to Google. |
Hi, I made this pull request to specifically address issue #13388. This PR fixes this, and allow fellow devs to continue working with their own builders setup while waiting for v8. To break circular dependencies, I had to move two declarations Sincerely sorry for the little mess with commits:
Finally, I'm not sure why two items of test-large failed on CI when it worked locally:
Thank you for your amazing work, I hope this edit can help. |
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.
Thanks for this, kindly squash all commits.
The failing test seems to be a flake.
CLAs look good, thanks! |
Well I just learned about squashing. I hope it's all good, Bot seems okay with this. EDIT: I'll be damned, these actions broke linting again. Back to it... |
…build_angular schemas. Fixes issue angular#13388
Okay seems all good to me. I believe the last One last thing though, as this PR moves two declarations, do you think we should export back these two types from
Kinda ugly but it might prevent further issues ? EDIT: Just checked, it wouldn't break linting. |
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.
Thanks LGTM
@opulisDynamics I don't see the need for that. |
My build was fixed with "@angular-devkit/build-angular": "0.13.9". Thanks folks. |
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. |
…in build_angular schemas.
Fixes issue #13388