node-lookml-parser
node-lookml-parser copied to clipboard
Parse LookML in Node
Currently, all tests only exercise index.js as the entrypoint, which allowed v6.6 to be published with an error in cli.js (the entrypoint used for the command-line invocation). Add some tests...
Probably because we hoist manifest out of files, but then look through files for errors 
Creating this issue for posterity, but I already started working on this feature a while back. Currently round-tripping is possible, but I have to add a routine to mark already...
Right now the parser does not do any parsing within blocks/strings (sql, html, etc) Inspecting these blocks could users more conveniently pick out references, e.g. in ${} substitution or {{}}...
Hey @fabio-looker - I *think* we uncovered a bug whereby `lookml-parser` fails on large (~800 files) projects: https://github.com/WarbyParker/lookmlint/issues/50#issuecomment-447420100 Didn't know if you had seen that before, or had any immediate...
The following part of the grammar needs to be tweaked slightly to allow for _ to be consumed without any actual declaration: 
Hi Fabio, I am very new to Looker, but am keen to see if your tool could be used to extract dependencies to our datasource. It seems to work very...
TODO: Confirm what exactly Looker accepts... ``` explore: users { fields: [ ALL_FIELDS*, - users.pii, - users.other_pii ] } ```
Consider accepting this unexpectedly passing syntax (two colons)