-
There currently is no consistency in the casing of property names in our JSON resources and JSON output. The project was built piecemeal, but it's perhaps time to clean it up with a consistent use of …
-
I use eleventyNavigation on some pages which has indented key and order. Kirby overwrites the camelcase written eleventyNavigation and adds a pipe.
Before saving:
```
eleventyNavigation:
key…
-
It seems to me that libraries do not always appropriately handle camelCase property names the same way.
When using Vue and Svelte together, for example, I'm finding the only way to reliably pass pr…
-
Hey, if you're accepting PRs I'd be happy to help with this. I would tackle it as follows:
- [ ] refactor public API by creating camelCase wrappers that call the existing snake_case methods
- [ ] keep…
-
I naturally tend toward CamelCase, as evident in the recent merger. While it's not a huge deal, I should work toward switching over our internal interfaces to CamelCase. For consistency.
jvilk updated
8 years ago
-
"snakecase" documentation refers to camelCase to suggest the transformation of _someString_ to _some_string_ but then "camelcase" documentation refers to CamelCase suggesting _some_string_ is converte…
-
E.g. QLinearGradient is marked as error
-
I have a word in my project that is:
word="FOBO".
As it is only a word, the expected output when we do word.camelize() should be: "fobo", but it my case I´m getting "fOBO".
I suspect that humanize…
-
To match other Chapel standard module functions. This would change the name to `signBit`
-
Based on a brief conversation I had added https://github.com/abcxyz/readability/wiki/JSON-Best-Practices#camelcase-over-snake_case to the wiki, but after receiving [feedback preferring snake_case in a…