Travis Prescott
Travis Prescott
The error thrown is: ``` (ERROR) dataCorrupted(Swift.DecodingError.Context(codingPath: [], debugDescription: "The given data was not valid YAML.", underlyingError: Optional(154:19: error: composer: found undefined alias: - *ref_0 ^))) ```
The offending code begins at line 278 in Parser.swift: ```Swift func loadAlias(from event: Event) throws -> Node { guard let alias = event.aliasAnchor else { fatalError("unreachable") } guard let node...
Alternatively, if the parser could simply do an initial pass and NOT throw an error on unresolved aliases, then the alias would be constructed. If the parser could then reparse...
I have a draft PR in my local fork that is mostly working for me. https://github.com/tjprescott/Yams/pull/1
We are using this in our code generator and making heavy use of Codable. Right now it seems to be working for our purposes (we are unblocked) but I'm sure...
We have a hacky workaround in my fork that we are using. It by no means is a general solution. I think that would require, as you noted, a fundamental...
I just encountered this as well. Our current workaround it to replace all empty strings in our YAML file with a single space.
This API should be reviewed by the API Stewardship Board due to the breaking changes present.
@raosanat can you transfer this to your repo for action?
@raosanat can you take a look at this?