Skip to content

chore(yarn-cling): rename test packages to real package names#16325

Merged
mergify[bot] merged 4 commits intomasterfrom
njlynch/yarn-cling-real-packages
Sep 1, 2021
Merged

chore(yarn-cling): rename test packages to real package names#16325
mergify[bot] merged 4 commits intomasterfrom
njlynch/yarn-cling-real-packages

Conversation

@njlynch
Copy link
Copy Markdown
Contributor

@njlynch njlynch commented Sep 1, 2021

The tests for yarn-cling currently reference what were imaginary package names
as placeholders; those package names have now been registered. While this has no
practical impact, switching the package names to be ones we own just so there's
no ambiguity.

An npm install is never done on these directories, so the packages chosen really
doesn't matter. Just picked two of our favorites at random. :)


By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license

The tests for `yarn-cling` currently reference what were imaginary package names
as placeholders; those package names have now been registered. While this has no
practical impact, switching the package names to be ones we own just so there's
no ambiguity.
@njlynch njlynch requested a review from a team September 1, 2021 16:22
@njlynch njlynch self-assigned this Sep 1, 2021
@gitpod-io
Copy link
Copy Markdown

gitpod-io bot commented Sep 1, 2021

@mergify mergify bot added the contribution/core This is a PR that came from AWS. label Sep 1, 2021
@njlynch njlynch requested a review from nija-at September 1, 2021 16:43
@nija-at nija-at added the pr/do-not-merge This PR should not be merged at this time. label Sep 1, 2021
Copy link
Copy Markdown
Contributor

@nija-at nija-at left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should this also be applied to package1?

@njlynch
Copy link
Copy Markdown
Contributor Author

njlynch commented Sep 1, 2021

Should this also be applied to package1?

It's not referenced as a dependency in a package.json file, so there's no confusion about someone accidentally running npm install and getting the wrong thing. That being said, might as well. I renamed it to jsii. :)

@njlynch njlynch removed the pr/do-not-merge This PR should not be merged at this time. label Sep 1, 2021
@mergify
Copy link
Copy Markdown
Contributor

mergify bot commented Sep 1, 2021

Thank you for contributing! Your pull request will be updated from master and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork).

@aws-cdk-automation
Copy link
Copy Markdown
Collaborator

AWS CodeBuild CI Report

  • CodeBuild project: AutoBuildProject89A8053A-LhjRyN9kxr8o
  • Commit ID: 9d7cc72
  • Result: SUCCEEDED
  • Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

@mergify mergify bot merged commit 839fdb9 into master Sep 1, 2021
@mergify mergify bot deleted the njlynch/yarn-cling-real-packages branch September 1, 2021 18:20
@mergify
Copy link
Copy Markdown
Contributor

mergify bot commented Sep 1, 2021

Thank you for contributing! Your pull request will be updated from master and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork).

madeline-k pushed a commit to madeline-k/aws-cdk that referenced this pull request Sep 2, 2021
)

The tests for `yarn-cling` currently reference what were imaginary package names
as placeholders; those package names have now been registered. While this has no
practical impact, switching the package names to be ones we own just so there's
no ambiguity.

An `npm install` is never done on these directories, so the packages chosen really
doesn't matter. Just picked two of our favorites at random. :)

----

*By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
TikiTDO pushed a commit to TikiTDO/aws-cdk that referenced this pull request Sep 6, 2021
)

The tests for `yarn-cling` currently reference what were imaginary package names
as placeholders; those package names have now been registered. While this has no
practical impact, switching the package names to be ones we own just so there's
no ambiguity.

An `npm install` is never done on these directories, so the packages chosen really
doesn't matter. Just picked two of our favorites at random. :)

----

*By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
david-doyle-as24 pushed a commit to david-doyle-as24/aws-cdk that referenced this pull request Sep 7, 2021
)

The tests for `yarn-cling` currently reference what were imaginary package names
as placeholders; those package names have now been registered. While this has no
practical impact, switching the package names to be ones we own just so there's
no ambiguity.

An `npm install` is never done on these directories, so the packages chosen really
doesn't matter. Just picked two of our favorites at random. :)

----

*By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

contribution/core This is a PR that came from AWS.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants