Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Fix: Windows path parsing for JUnit (fixes #12507) #12509

Merged
merged 2 commits into from Dec 23, 2019
Merged

Fix: Windows path parsing for JUnit (fixes #12507) #12509

merged 2 commits into from Dec 23, 2019

Commits on Oct 30, 2019

  1. Fix: Windows path parsing for JUnit (fixes eslint#12507) 

    This commit aims to fix the issues described in eslint#12507 by removing the
assumption that POSIX style filePaths are supplied by messages.

The tests for this are also updated to run on both Windows and POSIX
based systems. The results can be seen by running ESLint with the JUnit
formatter on a Windows system.

Full details can be seen in the issue mentioned above.
    @thewalla07
    thewalla07 committed Oct 30, 2019
    Copy the full SHA
    a0ddb2d View commit details
    Browse the repository at this point in the history

Commits on Nov 8, 2019

  1. Fix: use const instead of function 

    Addresses some comments.
    @thewalla07
    thewalla07 committed Nov 8, 2019
    Copy the full SHA
    fcdd913 View commit details
    Browse the repository at this point in the history