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.

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

Errors don't get reported if there's a parsing error #19

Open
IPWright83 opened this issue Oct 2, 2019 · 0 comments
Open

Errors don't get reported if there's a parsing error #19

IPWright83 opened this issue Oct 2, 2019 · 0 comments

Comments

@IPWright83
Copy link

IPWright83 commented Oct 2, 2019

I've found that despite xo working on the command line (and seen it working in other editors) if I introduce a syntax error then I get an ok report from xo in Sublime instead of an error.

Here's a small example:

const { test } = require("./test");

describe("test", () => {

    it("bad foo", () => {
        foo();
    });

    it("bad syntax", () => {
        await test();
    })
});

If you run this in a different editor (e.g. Atom) or via the command line it'll complain about line 10 having an await not inside an async function. I'd expect this to highlight as an error.

The result is it looks like the file is ok, however if you add the async back into the function declaration then you see there are actual errors that need fixing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants