Skip to content

Moving config parsing to serde #272

@ChristopherJMiller

Description

@ChristopherJMiller

I believe a lot of complexity could be removed by swapping config parsing from a manually process with yaml-rust to object deserialization with serde with it's derive feature and a supporting yaml deserializer.

The Intermediate types could be removed as the deserializer understands optional parameters. To handle defaults, the attributes on config can be made private and getters can be implemented that access self and unwrap to a default if they were not set. The mode "serial" or "parallel" can be mapped properly via the derive attribute macros on enums.

This could also ease the work involved with #265

Thoughts?

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions