Google Git
Sign in
android / platform / external / rust / crates / heck / refs/tags/android-r-beta-2
tag523a787fee7d2a90973f34d47f517919167fd072
taggerThe Android Open Source Project <initial-contribution@android.com>Tue Jul 14 15:06:31 2020 -0700
object756195ff099c82ce5c492ae4a201cb1d2ca24001 
Android R Beta 2
commit756195ff099c82ce5c492ae4a201cb1d2ca24001[log] [tgz]
authorChih-Hung Hsieh <chh@google.com>Tue Jul 07 11:50:50 2020 -0700
committerChih-Hung Hsieh <chh@google.com>Tue Jul 07 11:58:05 2020 -0700
tree9b63c6690ab9d5dedf8eb11eae02a3f9d35e6713
parentb9c6c14cca18afa346c1fc036b90c626979a8803 [diff]
Add OWNERS

Bug: 158624751
Test: make
Change-Id: I9add6b0714e934c637da7b73cd7a88760970094a
1 file changed
tree: 9b63c6690ab9d5dedf8eb11eae02a3f9d35e6713
  1. src/
  2. LICENSE ⇨ LICENSE-APACHE
  3. NOTICE ⇨ LICENSE
  4. .cargo_vcs_info.json
  5. .gitignore
  6. Cargo.toml
  7. Cargo.toml.orig
  8. LICENSE-APACHE
  9. LICENSE-MIT
  10. METADATA
  11. MODULE_LICENSE_APACHE2
  12. no_step_on_snek.png
  13. OWNERS
  14. README.md
README.md

heck is a case conversion library

I specifically requested the opposite of this.

This library exists to provide case conversion between common cases like CamelCase and snake_case. It is intended to be unicode aware, internally consistent, and reasonably well performing.

Definition of a word boundary

Word boundaries are defined as the “unicode words” defined in the unicode_segmentation library, as well as within those words in this manner:

  1. All underscore characters are considered word boundaries.
  2. If an uppercase character is followed by lowercase letters, a word boundary is considered to be just prior to that uppercase character.
  3. If multiple uppercase characters are consecutive, they are considered to be within a single word, except that the last will be part of the next word if it is followed by lowercase characters (see rule 2).

That is, “HelloWorld” is segmented Hello|World whereas “XMLHttpRequest” is segmented XML|Http|Request.

Characters not within words (such as spaces, punctuations, and underscores) are not included in the output string except as they are a part of the case being converted to. Multiple adjacent word boundaries (such as a series of underscores) are folded into one. (“hello__world” in snake case is therefore “hello_world”, not the exact same string). Leading or trailing word boundary indicators are dropped, except insofar as CamelCase capitalizes the first word.

Cases contained in this library:

  1. CamelCase
  2. snake_case
  3. kebab-case
  4. SHOUTY_SNAKE_CASE
  5. mixedCase
  6. Title Case

Contributing

PRs of additional well-established cases welcome.

This library is a little bit opinionated (dropping punctuation, for example). If that doesn't fit your use case, I hope there is another crate that does. I would prefer not to receive PRs to make this behavior more configurable.

Bug reports & fixes always welcome. :-)

License

heck is distributed under the terms of both the MIT license and the Apache License (Version 2.0).

See LICENSE-APACHE and LICENSE-MIT for details.