feat: support more case options #41
Merged
Conversation
This file contains 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
|
Thanks ! I was thinking of doing something like this in the future but I never got around doing it. The name changes seem reasonable ! I'll merge this and release a new version. Thanks again ! |
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.
Hey, nice library! I was just about to write my own stringifier, but then I discovered this existed. Unfortunately, it doesn't support everything I needed. Specifically, the case conversion. So I added some more. I was originally going to write them by hand, but then I discovered that this exists, so I just based it on that.
One downside of doing it like this is what was formerly "lower" and "upper" are now "flat" and "upper_flat". Let me know if you don't like this or whatever.