he/him 
There’s so much to infer from this screenshot about what I’m working on, that I’m surprised nobody has called me out.
Show this thread
More JS tools should provide actionable hints when reporting errors. Especially important for begineers. Shown is an example from a tool I'm working on.pic.twitter.com/Ox3sFlhcz2
-
-
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
I agree, it would be hard to cover all bases though
-
For most syntax errors, I've found that you can generally provide hints for what the developer might have meant.
- 2 more replies
New conversation -
-
-
Was begineers on purpose? A mix of beginner and engineer? Cause I’m stealing that.
-
Oops, it wasn't! But that's a great mix.
End of conversation
New conversation -
-
-
so awesome! haha I remember this issue from https://github.com/babel/babylon/issues/113 …, there was a PR to fix in Babylon but got kinda complicated in other cases and we never landed it. We should do it anyway for the simple case like you've shown here
-
It's best when you can produce multiple code frames, which isn't really tenable for something like Babel which can't make any assumptions. You can just add a check for state.inFunction in checkReservedWord
End of conversation
New conversation -
-
-
Hey :) I'd be really interested to learn more about how you are able to find the right column and character of the issue! Do you parse the code yourself and track the tokens?
-
It’s a custom parser, I keep track of the current function location in state and use that to infer the hint.
- 3 more replies
New conversation -
-
-
Agreed! We already do pretty well here, but we might steal the idea for a related span
pic.twitter.com/nT4GY5GXfp -
The related span went in today thanks to
@uhyo_
https://github.com/Microsoft/TypeScript/pull/31194 …
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.