Multiline operator placement, jsx-a11y/label adjusments

• Require linebreaks be placed before operators. Change operator-linebreak from after to before to keep terms in multi-line expressions on the same line.
• Turn off label-has-for, it’s been deprecated.
• Turn off label-has-associated-control, because it is a nightmare to have to keep a list for styled-component names that output label or input/select/textarea.

v7 Update to comma dangle (enforce on multi-line)

Change dangling comma policy

• Always require comma dangle on multiline
• Change version to 7, as the rule change will break existing builds

fixed version in package.json

v6.1.1

6.1.1

Version 6.1.0: Update eslint-compat & eslint-import

• Updated eslint-plugin-compat from 1.0.4 > 2.0.1
• Updated eslint-plugin-import from 2.7.0 > 2.8.0
• No new rules added, definition for "import/exports-last", added but disabled

Version 6

• Turning off multiline-ternary rule. Going to rely on developer common sense instead. Use case:

{teamATable && teamBTable ? ( // eslint-disable-line multiline-ternary
    <PlayerStatsButtonRow
        key="row"
        teamAName={teamAName}
        teamBName={teamBName}
        teamAId={teamAId}
        teamBId={teamBId}
        showTeam={showTeam}
        onClickShowTeam={onClickShowTeam} />
    ) : (
        <PlayerStatsPlaceholder />
    )
)}

• Added commonJS/node.js rules, however note they are NOT being imported into the base package
• Added .skip to test rule errors

Version 5

Updating eslint-plugin-react to 7.4.0

Added new react linting rules.

Version 4

Updating jsx-a11y from 3.0.2 to 6.0.2

Much more robust accessibility linting for react components

Added eslint-plugin-import rules

• Added eslint-plugin-import rules
• Tweaked some existing react rules
• Added warnings for TODO comments

Version 3

Updated eslint to 4.1.1 with associated core rules changes

• stricter ES6 syntax enforcement - const, return, destructuring
• made line length more lenient - ignores URLs or string literals
• changed config setup for "browser compat" plugin - appears to have changed?
• updated readme
• added plugin versions to package.json as optionalDependencies