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
Feel free to up-vote, but I think the current set of features supports the uses cases the Dart team have for parsing configuration files.
If you want advanced custom syntax, then why not a fully fledged parser for a domain specific language using something like package:petitparser. If you search for "yaml bad" or look at compatibility results from yaml-test-suite, then there are plenty of good reasons not to use YAML for DSLs with complex syntax. I would suggest writing a parser instead.
If you really want custom tag support I think it might be best implemented in a community package. Adding such features here are liable to cause more bugs, and it's not clear that this is something we need in Dart tooling or that most users of package:yaml needs.
Currently, in the public API tags aren't exposed at all. Is there any reason for that? This makes custom tags (like
!Foo
) completely disappear.The text was updated successfully, but these errors were encountered: