Skip to content

feat: additional devEngines checks #9742

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

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

danielbayley
Copy link

@danielbayley danielbayley commented Jul 11, 2025

@GeoffreyBooth
Copy link

I don't feel familiar enough with the pnpm codebase to review this, but if there were documentation added I could review that.

@danielbayley
Copy link
Author

I don't feel familiar enough with the pnpm codebase to review this

There’s only really this logic to go over here, which is not particularly entangled with the rest of the code. @zkochan might like some changes, but I doubt anything drastically different to what I sketched out there, other than maybe potentially generalising checkPackageManager() and reusing that…

if there were documentation added I could review that.

Yeah that’ll be the last step, after approval.

@GeoffreyBooth
Copy link

Yeah that’ll be the last step, after approval.

Maybe this is my bias coming from other projects, but generally what I'm used to is starting with documentation, and reaching agreement on that, so that everyone is aligned on what the intent of the PR is. Then the code review is just about whether or not there are bugs and whether it correctly implements the intent as described in the documentation.

@danielbayley
Copy link
Author

Yeah that’ll be the last step, after approval.

Maybe this is my bias coming from other projects, but generally what I'm used to is starting with documentation, and reaching agreement on that, so that everyone is aligned on what the intent of the PR is. Then the code review is just about whether or not there are bugs and whether it correctly implements the intent as described in the documentation.

That’s a fine approach, and one Iv’e taken at times, but in this particular case we kind of already have that in the form of your existing spec, no?

Copy link

@wesleytodd wesleytodd left a comment

Choose a reason for hiding this comment

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

Similar to @GeoffreyBooth, I do not have enough familiarity with the pnpm codebase to be a good reviewer and would love to see docs, but the checks seem correct to me at first glace.

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.

3 participants