You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In some cases, a Looker user may commit LookML and request Spectacles validation for LookML that was not written in Looker's web IDE. In these cases, the ability to run LookML validation via Spectacles would be helpful because it would catch syntax errors that can cause confusing errors in other validators (like the SQL validator).
We should add a new validator, like spectacles syntax, or similar, that runs Looker's LookML validator via the API and returns the results.
The text was updated successfully, but these errors were encountered:
Dropping in: I can confirm, that this problem can arise in real-world-scenarios where a user pull the code locally to perform e.g. many file / folder structure based operations and/or 'heavy copy-pasting' between different files.
In cases like this, a user might prefer the power of a good local text editor over the brower based Looker web IDE UI.
Looking forward to get the fix to this live in Spectacles :-)
In some cases, a Looker user may commit LookML and request Spectacles validation for LookML that was not written in Looker's web IDE. In these cases, the ability to run LookML validation via Spectacles would be helpful because it would catch syntax errors that can cause confusing errors in other validators (like the SQL validator).
We should add a new validator, like
spectacles syntax
, or similar, that runs Looker's LookML validator via the API and returns the results.The text was updated successfully, but these errors were encountered: