Andrey Somov

> > [@asomov](https://github.com/asomov) I have started the migration, but the tests in the main branch failed: > > I can spare some time and can help if needed, assuming it'll...

Unfortunately, I do not know know how to change SnakeYAML Engine - some checks can only be done when the Node tree is created.

@headius I created [a ticket to investigate](https://bitbucket.org/snakeyaml/snakeyaml-engine/issues/54)

The bug in SnakeYAML Engine is reproduced. We will have a look.

It is related to the previous issue: https://bitbucket.org/snakeyaml/snakeyaml/issues/485/alias-names-are-too-permissive-compared-to It is not yet solved in the spec: https://github.com/yaml/yaml-spec/issues/75 When anchor/alias may not contain a colon, the space will not be required....

the explanation for libyaml: https://github.com/yaml/libyaml/issues/205#issuecomment-693634465

@headius please check [the changes in the tests](https://bitbucket.org/snakeyaml/snakeyaml-engine/pull-requests/16) The colon is not accepted now in the name of anchor and the extra separating space is not required

@headius I assume [the PR in SnakeYAML](https://bitbucket.org/snakeyaml/snakeyaml-engine/pull-requests/16) delivers what is expected.

@headius I will merge the PR

@perlpunk I see your proposal as confusing. Parser should emit redundant space to satisfy other parsers (which should better implement the deviation from the spec to be consistent). @headius well,...