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
Having the source location of events within Text.Libyaml is useful for printing error/warning messages related to documents. If the marks are available, the Data.YamlParseException constructors could (possibly) include the mark related to the monad failure. I haven't looked in depth into the way the Aeson bindings have been done, so maybe that's not possible. But adding location information to errors in Data.Yaml.Parser should be possible. Having the marks in Text.Libyaml would be the minimum necessary to meet what I need (according to the libyaml documentation, start_mark and end_mark attributes are available for all events).
The text was updated successfully, but these errors were encountered:
Having the source location of events within
Text.Libyaml
is useful for printing error/warning messages related to documents. If the marks are available, theData.Yaml
ParseException
constructors could (possibly) include the mark related to the monad failure. I haven't looked in depth into the way the Aeson bindings have been done, so maybe that's not possible. But adding location information to errors inData.Yaml.Parser
should be possible. Having the marks inText.Libyaml
would be the minimum necessary to meet what I need (according to the libyaml documentation,start_mark
andend_mark
attributes are available for all events).The text was updated successfully, but these errors were encountered: