-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
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
Ruby reserved words in filters #4
Comments
By looking at the code I was not able to find out how the arguments to the |
Glug uses As a workaround, you can define the key as an object explicitly:
and then refer to it from then onwards like this:
Going forward, I think the best way to solve this would be a short-form version of the above, where you could write |
Thanks for the explanation! Your workaround did it for me. |
Fixed in 0a20718. |
Advance warning: this will change to |
I'm using a datasource (http://osm2vectortiles.org), which makes extensive use of the column name "class". Using this in filters leads to errors. I think this has something to do with "class" being a reserved word. But also writing
on('class'=='residential')
yields the following error:Is there another way of using reserved words I'm missing or does something in the code of Glug need changing? @systemed
The text was updated successfully, but these errors were encountered: