Skip to content

Add support for allowNegative ("--no-foo")#163

Merged
bakkot merged 2 commits into
mainfrom
allownegative
Jul 27, 2025
Merged

Add support for allowNegative ("--no-foo")#163
bakkot merged 2 commits into
mainfrom
allownegative

Conversation

@bakkot

@bakkot bakkot commented Jun 27, 2025

Copy link
Copy Markdown
Collaborator

Fixes #160; cc @ljharb.

Direct port of nodejs/node#53107. Node is MIT licensed, same as this project, so that should be kosher. I added the original author as a coauthor on the commit.

Co-authored-by: Zhenwei Jin <109658203+kylo5aby@users.noreply.github.com>

@ljharb ljharb left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Love it! Confirmed it matches the node commit.

@ljharb ljharb requested a review from shadowspawn June 27, 2025 05:26
@bakkot

bakkot commented Jun 27, 2025

Copy link
Copy Markdown
Collaborator Author

oh, should update the readme too I guess

edit: done

@shadowspawn shadowspawn left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

LGTM, thanks @bakkot

@bakkot

bakkot commented Jul 27, 2025

Copy link
Copy Markdown
Collaborator Author

Gonna go ahead and click the merge button.

I'm not sure how releases here work. Looks like there's a github workflow referencing an archived action? Anyway I think it would be good to do a release.

@bakkot bakkot merged commit bb2c69c into main Jul 27, 2025
10 checks passed
@bakkot bakkot deleted the allownegative branch July 27, 2025 00:25
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.

need to implement allowNegative option

3 participants