Add elements project type for boilerplate example projects#33484
Add elements project type for boilerplate example projects#33484yallen011 wants to merge 1 commit intoangular:masterfrom
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. ℹ️ Googlers: Go here for more info. |
|
@googlebot I fixed it. |
|
CLAs look good, thanks! ℹ️ Googlers: Go here for more info. |
47d859d to
8c0699d
Compare
61c9fe8 to
66e1a17
Compare
|
You can preview 47d859d at https://pr33484-47d859d.ngbuilds.io/. |
petebacondarwin
left a comment
There was a problem hiding this comment.
Great first PR @yallen011 !!
One small change please. In the commit message you don't need to add the PR Close #31332 line.
Our merge script will add this line with a link back to this PR. Please can change that line in your commit message to
Fixes #31332
gkalpak
left a comment
There was a problem hiding this comment.
Thx, @yallen011 ✨
I left a couple more comments, but otherwise this lgtm 👍
|
Ok, I will make the changes and resubmit. |
gkalpak
left a comment
There was a problem hiding this comment.
One minor comment, but otherwise lgtm 🎉
Also, please, update the commit message (which is already in a pretty good form) to more closely follow our guidelines:
fix(docs-infra): add boilerplate path and project type for elements example project
Fixes #31332
There was a problem hiding this comment.
Incorrect aplhabetic order: core should be above elements 😃
|
Oh, also, please rebase on master to make CI green. |
|
Hi @gkalpak I read the doc for the commit message again, but I'm not sure what needs to be modified. |
|
I've included a suggested commit message in my previous comment 😃 #33484 (review) |
|
BTW, it seems you also need to rebase on master to make CI green. (You can follow the instructions in #33829 (comment).) |
|
Ok, I see. I misread the comment asking me to change |
|
Both The current commit message is:
My suggestion is to change it to:
(LMK if you run into difficulties updating the commit message or rebasing. Thx again for working on this 👍) |
|
@gkalpak that's the way I had it at first. On a new line at the bottom of the commit message. |
|
@yallen011, according to GitHub this is the initial PR commit 🤷♂ |
c082cf0 to
1728e63
Compare
|
ok, updated changes and forced pushed to kick off CI job |
|
You can preview 1728e63 at https://pr33484-1728e63.ngbuilds.io/. |
|
@gkalpak I think this commit is ready to merge can you please have a look |
gkalpak
left a comment
There was a problem hiding this comment.
Thx for making the changes, @yallen011! LGTM ✨
I've totally missed that I needed to re-review this. Thx for the ping, @ajitsinghkaler 👍
|
@yallen011 please rebase. |
…xample project Fixes angular#31332
1728e63 to
4b8f7fe
Compare
|
Rebased on master. |
|
@gkalpak do we need to update Angular package versions from |
|
@AndrewKushnir, this should be merged as is (to be consistent with the rest of the examples). I am updating the examples to v9/Ivy in #34374. |
|
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. |


Added elements project type to the boilerplate sample projects to fix the issue with the angular elements example project in the Angular docs needing to be updated due to the angular elements package not being present in the
package.jsonfile when the zip file is downloaded.PR Checklist
Please check if your PR fulfills the following requirements:
PR Type
What kind of change does this PR introduce?
What is the current behavior?
When downloading the zip from the https://angular.io/generated/zips/elements/elements.zip the
@angular/elementspackage is not included in thepackage.jsonIssue Number: #31332
What is the new behavior?
the
@angular/elementspackage should now be included when downloading the following zip mentioned above.Does this PR introduce a breaking change?
Other information