fabio-looker

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...

Convenience feature. Probably with a command line flag

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 {{}}...

The following part of the grammar needs to be tweaked slightly to allow for _ to be consumed without any actual declaration: 

Via the api, secrets can now be created that are bound to being used with HMAC-SHA-256 instead of HMAC-SHA-1. Add a feature to allow users to test these secrets. https://docs.looker.com/reference/api-and-integration/api-reference/v4.0/auth

Under `There is no request for the SSO Embed URL (like /login/embed/...)` `Mixed Content: The page at 'https://' was loaded over HTTPS, but requested an insecure resource 'http://'. This request...

Ability to provide a second host (and embed secret) and to compare two side by side embeds. Useful for testing releases and staging vs prod

TODO: Confirm what exactly Looker accepts... ``` explore: users { fields: [ ALL_FIELDS*, - users.pii, - users.other_pii ] } ```