pkg: update description to mention current features #123
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
- all the things I've added since ~v1.0.0-ish - this branch has been laying here for a few years now too and I think I forgot about it 😅
This comment was marked as resolved.
This comment was marked as resolved.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Add "100% test coverage, types, examples, & more." to the
package.json#descriptionDetails
Verification
The NPM docs do not indicate a character limit on
description, but I was concerned about that, so also tested withnpm packand no errors.Future Work
I may remove the
react-signature-padreference eventually as this fork has now existed independently for longer than the original existed before my fork. I've been planning to "unlink" the fork it once the TS release (#42) is finally out to simplify SEO, PRs1, and reduce user confusion with all the links at the top of the repo. Will still have it mentioned in the description as historical context ofc, just no longer top-of-mind for the initial descriptionFootnotes
By default it makes my PRs go to the original repo /
react-signature-padand requires a few clicks to redirect tomainof this repo, and users occasionally click the PR button at the top of the repo too ↩