This repository was archived by the owner on Mar 8, 2020. It is now read-only.
Repository navigation
This repository was archived by the owner on Mar 8, 2020. It is now read-only.
Strange <nil> token. Should be None? #99
Description
I found it in my visualization example:
https://gist.github.com/zurk/d314d67d9aac8843d3776c82cd738b40
8 || ┣ BINARY, THIS, EXPRESSION
8 |var1| ┃ ┣ LEFT, IDENTIFIER, EXPRESSION
7 || ┃ ┃ ┣ INCOMPLETE
7 |\n| ┃ ┃ ┗ ┗ DOCUMENTATION
8 |<nil>| ┃ ┗ BYTE, NUMBER, EXPRESSION, RIGHT
If you take a look at the code, you will see that actually corresponds to None token.
Also, I doubt that None should have a NUMBER role, maybe NULL?
Activity
zurk commentedon Sep 27, 2017
ok, If you just parse
Nonevia Babelfish, you will have this tree:and I expected to get something like:
May be something else, idk.
zurk commentedon Sep 27, 2017
Also
THISrole is strange in the example.juanjux commentedon Sep 28, 2017
Was because of the desync between the SDK numeric roles, fixed in the latest version that should be incorporated in the python-driver 1.0.3 image.
It's
Literal, Null, Expressionin the last version.zurk commentedon Sep 28, 2017
Yes, but the main question of issue is about
<nil>token. It should beNoneI think.juanjux commentedon Sep 28, 2017
Oh I skipped that one, sorry!
I'll be fixed in PR #112 which includes misc annotation fixes (mostly from your reports). It'll probably be merged in version 1.0.4 of the driver, but this version could take some time since we're in the middle of a refactor of several components.
juanjux commentedon Sep 29, 2017
Fixed by #112 and #113 when merged.