Commit 353d24d
committed
JS: enforce camel case (#38)
We seem to be bad at sticking to this rule, so I think it's worth
enforcing it.
I think part of why we haven't done this before is that we were afraid
of triggering this on code interacting with JSON fields from API
responses, which generally *are* underscored. From my local testing,
I actually don't think that's a concern: the rule seems to trigger on
assignment/creation (`var foo_bar`, `{ name_blah: true}`, etc.), but not
access (e.g. `thing.foo_bar()` and `thing["attr_name"]` don't trigger
this).
Thoughts, @codeclimate/review?1 parent 29c5ebb commit 353d24d
1 file changed
+2
-1
lines changed| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
3 | 3 | | |
4 | 4 | | |
5 | 5 | | |
6 | | - | |
| 6 | + | |
7 | 7 | | |
8 | 8 | | |
9 | 9 | | |
| 10 | + | |
10 | 11 | | |
11 | 12 | | |
12 | 13 | | |
| |||
0 commit comments