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

readme: add description of --no behaviour #48

Merged
1 commit merged into from
Mar 2, 2024

Conversation

shadowspawn
Copy link
Collaborator

As a light-weight approach I just added an example usage to the long example. I started to document --no-foo explicitly, but it felt disproportionate for a small feature against the rest of the documentation.

Also, I removed old security warning. It has been quite a while since the original reports and fixes. I found it a bit stale and alarmist, but don't mind keeping it if preferred.

Fixes: #38

@codecov-commenter
Copy link

codecov-commenter commented Sep 17, 2023

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 98.78%. Comparing base (74f90f1) to head (fb7c658).

❗ Your organization needs to install the Codecov GitHub app to enable full functionality.

Additional details and impacted files
@@           Coverage Diff           @@
##             main      #48   +/-   ##
=======================================
  Coverage   98.78%   98.78%           
=======================================
  Files           1        1           
  Lines         165      165           
  Branches       70       70           
=======================================
  Hits          163      163           
  Misses          2        2           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

README.md Show resolved Hide resolved
@ljharb ljharb added the documentation Improvements or additions to documentation label Sep 17, 2023
@shadowspawn shadowspawn marked this pull request as draft October 12, 2023 05:29
@shadowspawn
Copy link
Collaborator Author

After new discussion in #38, I think worth of some explanatory text in addition to the example.

Also, remove old security warning.

Fixes: minimistjs#38
@shadowspawn shadowspawn marked this pull request as ready for review October 12, 2023 06:07
@shadowspawn
Copy link
Collaborator Author

I (hopefully) matched the existing terminology and added a short description of a negated argument, in addition to --no-ding in the examples.

@shadowspawn shadowspawn changed the title Docs: add example of --no-foo readme: add description of --no behaviour Oct 12, 2023
@ljharb ljharb closed this pull request by merging all changes into minimistjs:main in 4761d0b Mar 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Truncated, falsy arguments starting with --no
3 participants