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
LS-proper-proper-fix-I-swear #164
LS-proper-proper-fix-I-swear #164
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I can also generate a debug log with the exciting script
script;
I suggest being more methodical than "hey look script validation no longer fails on this specific case".
I tried to be thorough; I looked at everything calling makeComment and makeToken, and saw that specific case. |
Please don't think I'm botching this ;A; |
Empty directives should probably be an error...
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think these are all the changes we need. Might be nice to have a second opinion, though.
Let me fire up my Fredg directory and check out the branch... |
builds for me. I ran
on 28 scripts in my scripts directory. I'm currently running my Autoscend evening turns in it. Nothing I know of is broken. It occurs to me that if we're revamping the parser, one thing we'll want is a library of good and bad files to test with, which can prove that our parser is acting correctly end-to-end. It wouldn't be unit tests, but complementary to them. Functional tests are good at finding things like this. |
fyi you can fetch PR branches via git:
Anyways. I'll merge this fix, then. I couldn't find anything else when staring at the code. |
:,(