You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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",()=>{awaittest();})});
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.
The text was updated successfully, but these errors were encountered:
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 anok
report fromxo
in Sublime instead of an error.Here's a small example:
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 anasync
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.The text was updated successfully, but these errors were encountered: