3 Commits (975419db5439c6ecb094bf9df53d659122ef44f9)

Author	SHA1	Message	Date
Whymarrh Whitby	bb4c4189fb	eslint: Enable more react/jsx-* rules (#7592)	5 years ago
Whymarrh Whitby	2e69f3233e	eslint: Enable more react/jsx-* rules (#7592)	5 years ago
Whymarrh Whitby	b0890b6b32	Enforce a single boolean attr notation in JSX (#7465) ... This changeset enables the ESLint rule enforcing a single notation for boolean attributes in JSX—explictly setting the value to `true` is no longer allowed (as it was never needed).[1] From the docs for JSX:[2] > If you pass no value for a prop, it defaults to `true`. [1]:https://github.com/yannickcr/eslint-plugin-react/blob/80935658/docs/rules/jsx-boolean-value.md [2]:https://reactjs.org/docs/jsx-in-depth.html#props-default-to-true I have chosen to use this default as it the most consistent with HTML (a la `checked` and `disabled`).	5 years ago
ricky	7181779576	Refactor `new-account.js` (#7312) ... * Start refactor * Use import syntax * Add create-account.component * Continue refactor * Add new line * Start using JSX and make tabs a bit more DRY * 👋 bye-bye hyperscript * These can be disabled when active * Start JSX in new account component * 👋 bye-bye hyperscript * Move newAccountNumber into container * Validate newAccountNumber prop	5 years ago