More clear error messages for invalid characters#35
Conversation
|
Not sure what's up with the CI build, a |
|
ci says:
|
|
LGTM 👌 |
|
Pushed a small change to help users differentiate the first-character message from the error later on. |
|
@JakeWharton @rjrjr @loganj anyone interested in merging this? |
|
LGTM, but can we figure out why the Travis is failing? |
|
I think this is it:
|
|
That passed. Pushed a small formatting fix for the .travis.yml file |
|
Sigh, and another -- I added the newline to the wrong place |
|
Green! |
|
Can I get a merge here? I think this is a good usability improvement that will head off more issues like #36 |
Tweaks invalid start- and end-of-token messages for clarity.
Inspired by #33, fixes #32 and fixes #34, probably #29 as well.