Skip to content

Support YAML anchors/aliases on deserialization #20

@Blacksmoke16

Description

@Blacksmoke16

With the implementation of #18, YAML input is now streamed, or read token by token as it comes in. This makes supporting aliases/anchors a bit tricky as there isn't way to "back up" the pull parser when an alias is encountered.

Currently there are two way I can see to fix this.

  1. Try to come up with something to keep track of/store the anchored elements and apply them when encountered again.
  2. Revert Yaml.deserialize to simply use the previous logic of loading it into memory to do the conversion.

1 would be most ideal, but 2 wouldn't be the end of the world.

Metadata

Metadata

Assignees

No one assigned

    Labels

    format:yamlkind:bugAn existing feature isn't doing something correctly

    Projects

    No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions