no-typos: Fix failing createClass test

[ljharb]

Per #1671 (https://github.com/yannickcr/eslint-plugin-react/pull/1671/files#diff-a36b384ace30edac8eacb00c170eed54R1277) and #1389, there's a commented out no-typos test that should be uncommented and fixed.

[alexzherdev]

I have a fix coming up for this, but that depends on #1827 to be merged.
I have one question though. I think the four commented out tests are really just two test cases which run with and without babel-eslint. Is that necessary in the case of createClass? I understood this comment to mean "one test for static properties with babel-eslint and one test for regular Component.propTypes = ... without babel-eslint". Do we need to also run non-babel-eslint tests with babel-eslint?

[ljharb]

It’s not necessarily required, but it is ideal. Different parsers produce different AST node names, with different node schemas, so its useful to run them all through multiple parsers.

[alexzherdev]

Ok, I have this ready. And it looks like #1827 is good to go, so I'll create a PR after that's done.