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
expected <string> but got <EOF> #2
Comments
Thank you for this report! This is fixed in fc4f17c. To answer your questions:
|
@mohd-akram Thanks, it work for simple json file now, but I have a little long json file, which cause the jawk command output:
|
Hmm, odd. Does this happen with JSON.awk too or just with jawk? Could you provide the file? If not, do you think you'd be able to reduce it to a small sample where the error happens? |
@mohd-akram It does not happen with JSON.awk 1.4.2. I'm trying to reduce it to a small sample, see you soon. |
The full file has another special character, which display as ^I when set option with :set list in vim, and it make a little hard for me to copy and paste the text. even to reduce it to a small sample. |
Hmm, okay. Could you paste the full error message that you get? I might be able to figure it out that way. EDIT: It seems you did paste the full error but it got parsed in a strange way due to markdown. It's better to wrap errors/code in triple backticks, like so:
Okay, I can reproduce the error now. |
This should be fixed in b5167c4. |
Thanks for you fixing. |
Thanks for the reports! |
This is the json file demo-blank-line.json content:
This is the jawk command line:
./jawk '{print _["log_valid_days"]}' demo-blank-line.json
and this is the command output:
if I remove the blank line of demo-blank-line.json to make it look like this:
and run the same command line again, then it output:
7
My questions is:
The text was updated successfully, but these errors were encountered: