-
-
Notifications
You must be signed in to change notification settings - Fork 36
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
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
❗ 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. |
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
841c3e6
to
d6fc238
Compare
I (hopefully) matched the existing terminology and added a short description of a negated argument, in addition to |
d6fc238
to
2f1953c
Compare
2f1953c
to
b8277e1
Compare
b8277e1
to
fb7c658
Compare
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