-
Notifications
You must be signed in to change notification settings - Fork 290
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
detect mixed spaces/tabs or missing parameters #338
Comments
Tabs are technically forbidden in YAML, and Tangram's internal YAML parser has not resolved this since the issue was opened in 2013, even after the YAML spec creator weighed in: nodeca/js-yaml#80 The summary is that we have to catch these errors ourselves or do the work of patching js-yaml upstream. Incidentally, I have considered writing functionality in Tangram Play that can highlight these as errors, or convert them for you. We already insert spaces instead of a tab character when you press tab, so there's no chance of accidentally inserting tabs when authoring in Play. |
Illuminating: nodeca/js-yaml#80 (comment) – would it be worth considering libyaml at this point? |
Libyaml is python, I believe...? Is there a direct JS port? On Tue, Jun 21, 2016, 10:43 AM Peter Richardson notifications@github.com
|
Ah, missed that. Not to my knowledge. |
LibYAML is a C library, with bindings to many languages. It could probably be transpiled to JS with emscripten but I'm not aware that this has been done already. LibYAML also has a SAX-style parsing interface, which deterred us from using it in tangram-es. |
From the research I've done, I believe js-yaml is far and away the best JS YAML library. |
Let's patch it!![](https://link.nylas.com/open/c3ccrw0t3xj00dylcqc5uc6ma On Jun 21 2016, at 11:14 am, Brett Camper <notifications@github.com>
|
Closing with WONTFIX as out of scope. |
In this case the normal map just silently failed to draw, but the rest of the map did. Not sure how extensive the current internal linting is or if there's any kind of error which could be thrown in this case...
The text was updated successfully, but these errors were encountered: