judicial-hy / 0.200103

changelog.md 23.8 KB

eslint-friendly-formatter - Changelog

v4.0.1

  • Build Scripts Changes

  • Other changes

    Addresses issue #29. Message source can be null when a Parsing error is encountered.

  • Documentation

v4.0.0

v3.0.0

v2.0.7

v2.0.6

v2.0.5

  • Build Scripts Changes

  • Features

    The --eff-filter filters the rules shown in the report. Usefule to filter only a given type of rule.

    Example

    The following will only show the warning for global-require ruleId

    eslint -f node_modules/eslint-friendly-formatter client/**/*.js server/**/*.js -- --eff-by-issue --eff-filter 'global-require' # notice the --

  • Documentation

v2.0.4

v2.0.3

  • Build Scripts Changes

  • Features

    Eslint does not support passing arguments, but we can pass any parameters using -- --param-here. So now inside the reporter we can get the value like process.argv['--param-here']. This can be used to pass flags to the reporter so now we can do the following

    --eff-by-issue will group the report by issue type

    eslint -f 'node_modules/eslint-friendly-formatter' -- --eff-by-issue

  • Documentation

v2.0.2

v2.0.1

  • Build Scripts Changes

  • Refactoring

    • Add EFF_NO_LINK_RULES param. Fixes #18 - 7ed4647, Roy Riojas, 10/04/2016 02:44:06
    • In your terminal run
    export EFF_NO_LINK_RULES=true # rules ids won't be linked to
documentation

    Also as part of this commit, rules that contain /, a common pattern in eslint plugins, like react/jsx-quotes will generate a link to a google search for that rule.

  • Documentation

v2.0.0

v1.2.2

  • Build Scripts Changes

  • Features

    • Ignore source code when the source property is really (really) long!. Fixes #13 - a19ff73, Roy Riojas, 30/08/2015 08:36:40

  • Other changes

  • Documentation

v1.2.1

  • Build Scripts Changes

  • Other changes

    This happens when the javascript file has a parsing error.

  • Documentation

v1.2.0

v1.1.1

v1.1.0

  • Build Scripts Changes

  • Documentation

  • Features

    • add environment option EFF_ABSOLUTE_PATHS. Fixes #7 - 271a749, royriojas, 14/07/2015 01:20:57

    export the env variable EFF_ABSOLUTE_PATHS to make the paths in the reporter be absolute. If the environment variable is not found the paths will be reported as eslint send them.

    EFF_ABSOLUTE_PATHS=true eslint -f
path/to/eslint-friendly-formatter/index.js’ file1.js file2.js dir/

    Or

    add to your profile

    export EFF_ABSOLUTE_PATHS=true

    Ugly hack. But should work until this issue is resolved:

    https://github.com/eslint/eslint/issues/2989

  • Other changes

    Add Gulp to the list of working examples

    Better description of the when to disable the gray coloring

    Current master of Guake will also auto open a configured editor to the correct line number.

  • Cosmetic fixes

v1.0.8

v1.0.7

  • Build Scripts Changes

Changelog

v1.0.6

  • Build Scripts Changes

  • Bug Fixes

    • Support for solarized theme, or other themes that use gray for the background. Fixes #2 - a8c3c71, royriojas, 16/05/2015 17:02:33

    Basically this fix removes the gray color if the environment variable EFF_NO_GRAY is set to the string true.

    this can be done very easily in bash doing:

    export EFF_NO_GRAY=true

  • Other changes

  • Documentation

v1.0.5

  • Build Scripts Changes

  • Documentation

    • Better documentation for the integration with intellij or webstorm - 678886d, Roy Riojas, 18/03/2015 04:36:21

  • Enhancements

    • Use the full path to the file so IDEs like Webstorm or Intellij can parse the output - 4433a5e, Roy Riojas, 18/03/2015 04:15:50

v1.0.4