test(docs-infra): ensure RxJS-related docs examples can compile without errors#34063
test(docs-infra): ensure RxJS-related docs examples can compile without errors#34063sonukapoor wants to merge 2 commits 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. |
c8d87ba to
091109b
Compare
|
CLAs look good, thanks! ℹ️ Googlers: Go here for more info. |
70478f4 to
62032a9
Compare
There was a problem hiding this comment.
Thx, @sonukapoor! This is looking great already. I left a couple of comments.
Also, can you please update the commit message to something like:
test(docs-infra): ensure RxJS-related docs examples can compile without errors
Previously, some RxJS-related examples (which are not proper Angular apps) were not
tested on CI as part of theexample-e2enpm script. This meant that the examples
could get out-of-date or contain compile errors without as noticing.This commit ensures that the
example-e2escript picks up these examples and checks
that they compile successfully.Partly addresses #28017.
This should not close #28017, because that one is about adding tests (which this PR does not do).
|
@gkalpak All changes done, except the package.json one. Please suggest what should be done on that part. |
4a1da68 to
1a655a0
Compare
|
@gkalpak I have reverted the @types/node in root and add it to the shared package.json file. I also had to upgrade @types/jquery to 3.3.28. Please review. |
gkalpak
left a comment
There was a problem hiding this comment.
Great job, @sonukapoor 👏
Can you also please squash all commits together (and keep the commit message from a610a01be)?
5bfbf4c to
223ad81
Compare
223ad81 to
1b8cf27
Compare
…ut errors Previously, some RxJS-related examples (which are not proper Angular apps) were not tested on CI as part of the `example-e2e` npm script. This meant that the examples could get out-of-date or contain compile errors without as noticing. This commit ensures that the `example-e2e` script picks up these examples and checks that they compile successfully. Partly addresses angular#28017.
1b8cf27 to
a4fe600
Compare
|
All (the pull request submitter and all commit authors) CLAs are signed, but one or more commits were authored or co-authored by someone other than the pull request submitter. We need to confirm that all authors are ok with their commits being contributed to this project. Please have them confirm that by leaving a comment that contains only Note to project maintainer: There may be cases where the author cannot leave a comment, or the comment is not properly detected as consent. In those cases, you can manually confirm consent of the commit author(s), and set the ℹ️ Googlers: Go here for more info. |
|
@googlebot I consent. |
|
CLAs look good, thanks! ℹ️ Googlers: Go here for more info. |
|
merge-assistance: Global approval for this docs(-infra)-only change. |
…ut errors (#34063) Previously, some RxJS-related examples (which are not proper Angular apps) were not tested on CI as part of the `example-e2e` npm script. This meant that the examples could get out-of-date or contain compile errors without as noticing. This commit ensures that the `example-e2e` script picks up these examples and checks that they compile successfully. Partly addresses #28017. PR Close #34063
|
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. |
Some examples are simple typescript files. The changes in this PR make sure that they compile.
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?
Issue Number: #28017
What is the new behavior?
There is currently no way to validate code that is not an angular application e.g: The RxJS guide has no tests and no compilation steps. This PR adds a compilation step to at least validate the files.
Does this PR introduce a breaking change?
Other information