-
Notifications
You must be signed in to change notification settings - Fork 295
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
Parser Error reported - no further information provided to help me understand why it failed. #1703
Comments
The CodeExplorer should actually start displaying things already. The code has finished Parsing and is in the Resolving step. It seems these two things are still too tightly coupled and an error during Parsing doesn't correctly update the ParserState to Indicative of this are:
The problem lies therein that the Resolver Task doesn't correctly catch Exceptions before they bubble out into the last completed |
Can you post the code here maybe? I'd be especially interested in the
|
restLibrary appears to be this https://github.com/brucemcpherson/excelRestLibrary/blob/master/scripts/restLibrary.vba |
Thanks. Looks like that parses fine here in a reasonable amount of time (1sec, times 10 on a normal PC). |
There was no parser error. The trouble is the uncaught COM exception. |
Um... Interestingly one of the Code Inspections suggests to me to replace be explicit about parameters as they otherwise assumed to be variant. After asking CI to replace all occurance in the module, I had no idea the parser restarted and complained having a parse error hence the message. Interestingly the parser is complaining about my use of the word = False when altered to fix variant to become "False As" as shown below in red. |
@PeterMTaylor that's a bug in the inspection's quick-fix. I'm opening a new issue. ref. #1982 |
that's a different issue though. @retailcoder I think we can consider this one here fixed |
Using clone on commit 8428eb4 but referenced to my local git objects when error is detected.
I was surprised for RD to parse fail on a VBA code I was working on. I raise this issue because I could not see how I could not understand why it failed. The debug only provided a clue that it has failed and my options were limited in regards to no further information in determining why.
Failed twice.
The Code Explorer will not display anything except the Parser Error.
The text was updated successfully, but these errors were encountered: