8000 [YAML] spec example 5.3 is not parsed · Issue #8076 · symfony/symfony · GitHub
[go: up one dir, main page]

Skip to content

[YAML] spec example 5.3 is not parsed #8076

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

Closed
indeyets opened this issue May 17, 2013 · 4 comments
Closed

[YAML] spec example 5.3 is not parsed #8076

indeyets opened this issue May 17, 2013 · 4 comments
Labels

Comments

@indeyets
Copy link

http://www.yaml.org/spec/1.2/spec.html#id2772312

sequence:
- one
- two
mapping:
  ? sky
  : blue
  sea : green

Code above (taken from spec) results in Symfony\Component\Yaml\Exception\ParseException with message Unable to parse at line 6 (near "? sky").

@javiereguiluz
Copy link
Member

@indeyets thanks for reporting this error. You are right about Yaml component unable to parse that example. The reason is that currently the component doesn't support the entire YAML spec, but only the subset of features needed to define configuration files.

Considering all this, I think we should close this issue as won't fix.

@fabpot fabpot closed this as completed Sep 6, 2014
@xabbuh
Copy link
Member
xabbuh commented Sep 6, 2014

@javiereguiluz But maybe we can improve the error message. For example, we could provide a message like "The mapping key indicator character is not supported." What do you think?

@javiereguiluz
Copy link
Member

@xabbuh agree! Could you please open an issue to display (if possible) errors and warnings not only for this but whenever the developer tries to use any YAML feature not supported by the Yaml component? Thanks!

@xabbuh
Copy link
Member
xabbuh commented Sep 12, 2014

@javiereguiluz see #11911

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants
0