Skip to content

Remove AbstractNodeNodeTypeResolver workaround and use the feature #224

Closed

Description

@andrei2699

If AbstractNodeNodeTypeResolver is still needed, make sure to update it to not have build errors
If it is not needed, we can update the yamldotnet and update configurations to not need it

Initially AbstractNodeNodeTypeResolver was needed since YamlDotNet didn't support polymorphic types out of the box. In the mean time they do,
Se;;

Metadata

Metadata

Assignees

Labels

Type

Projects

No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions