We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
When using listener mode the parser is always expecting a line break after each line of python code. For instance,
const parser = new Python3Parser(); const python ='import sys\nfor i in sys.argv:\n print(i)'; // parseTree const tree = parser.parse(python); class MyListener extends Python3Listener { enterImport_name(ctx): void { let importName = ctx .getText() .toLowerCase() .match(/(?<=import).+/)?.[0]; console.log('ImportName', importName); } } const listenTableName = new MyListener(); parser.listen(listenTableName, tree);
The above code will work but when I remove '\n' from the python code it won't (Given below).
const parser = new Python3Parser(); const python ='import sys'; // parseTree const tree = parser.parse(python); class MyListener extends Python3Listener { enterImport_name(ctx): void { let importName = ctx .getText() .toLowerCase() .match(/(?<=import).+/)?.[0]; console.log('ImportName', importName); } } const listenTableName = new MyListener(); parser.listen(listenTableName, tree);
Is there a work around for this? I want to dynamically pass the python code to the parser so it might not always have a line break.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
When using listener mode the parser is always expecting a line break after each line of python code.
For instance,
The above code will work but when I remove '\n' from the python code it won't (Given below).
Is there a work around for this? I want to dynamically pass the python code to the parser so it might not always have a line break.
The text was updated successfully, but these errors were encountered: