Skip to content
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

Update Yarn constraints to remove reference to project/repo name #1032

Merged
merged 5 commits into from
Dec 19, 2022

Conversation

mcmire
Copy link
Contributor

@mcmire mcmire commented Dec 16, 2022

When creating the monorepo template, it was useful to revise the Yarn constraints file so that the project/repo name could be changed without having to change a bunch of references in the file. This commit brings over those revisions:

  • The repository URL is now used as a basis for the homepage URL and bugs URL, so it must be set appropriately (and if it is not, the user will see a suggestion in the correct format).
  • Additionally, the comments above each constraint have been reworded to be more consistent and understandable, and comments have been added where missing.
  • Finally, some pairs of constraints which test one thing for private packages and the opposite for public packages have been updated to apply to the root package vs. non-root packages where it made sense.

When creating the monorepo template, it was useful to revise the Yarn
constraints file so that the project/repo name could be changed without
having to change a bunch of references in the file. This commit brings
over those revisions:

* The repository URL is now used as a basis for the homepage URL and
  bugs URL, so it must be set appropriately (and if it is not, the user
  will see a suggestion in the correct format).
* Additionally, the comments above each constraint have been reworded to
  be more consistent and understandable, and comments have been added
  where missing.
* Finally, some pairs of constraints which test one thing for private
  packages and the opposite for public packages have been updated to
  apply to the root package vs. non-root packages where it made sense.
@mcmire mcmire requested a review from a team as a code owner December 16, 2022 21:07
@mcmire mcmire changed the title Update Yarn constraints to remove ref to project name Update Yarn constraints to remove reference to project/repo name Dec 16, 2022
@mcmire mcmire mentioned this pull request Dec 16, 2022
2 tasks
constraints.pro Outdated Show resolved Hide resolved
constraints.pro Outdated Show resolved Hide resolved
constraints.pro Outdated Show resolved Hide resolved
@Gudahtt
Copy link
Member

Gudahtt commented Dec 19, 2022

Thanks, this looks great! I had a few questions but no major concerns

Copy link
Member

@Gudahtt Gudahtt left a comment

Choose a reason for hiding this comment

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

LGTM!

@mcmire mcmire merged commit 08ddfcb into main Dec 19, 2022
@mcmire mcmire deleted the make-constraints-repo-name-agnostic branch December 19, 2022 21:12
MajorLift pushed a commit that referenced this pull request Oct 11, 2023
When creating the monorepo template, it was useful to revise the Yarn
constraints file so that the project/repo name could be changed without
having to change a bunch of references in the file. This commit brings
over those revisions:

* The repository URL is now used as a basis for the homepage URL and
bugs URL, so it must be set appropriately (and if it is not, the user
will see a suggestion in the correct format).
* Additionally, the comments above each constraint have been reworded to
be more consistent and understandable, and comments have been added
where missing.
* Finally, some pairs of constraints which test one thing for private
packages and the opposite for public packages have been updated to apply
to the root package vs. non-root packages where it made sense.
MajorLift pushed a commit that referenced this pull request Oct 11, 2023
When creating the monorepo template, it was useful to revise the Yarn
constraints file so that the project/repo name could be changed without
having to change a bunch of references in the file. This commit brings
over those revisions:

* The repository URL is now used as a basis for the homepage URL and
bugs URL, so it must be set appropriately (and if it is not, the user
will see a suggestion in the correct format).
* Additionally, the comments above each constraint have been reworded to
be more consistent and understandable, and comments have been added
where missing.
* Finally, some pairs of constraints which test one thing for private
packages and the opposite for public packages have been updated to apply
to the root package vs. non-root packages where it made sense.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants