Skip to content

Refactor DevDB InfoEntry #52

@jacob-curley-fnal

Description

@jacob-curley-fnal

In Rust projects, DevDB InfoEntry is being generated with a result field, which is an enum. The auto-generated enum has two values: one is a string, and the other is an object. Cargo's Clippy utility flags this as an issue. Essentially, it argues that if the data inside these enums are so wildly different in size, then they're probably too different to be one enum. We should look at refactoring the definition here so that errors and data are more clearly delineated.

Metadata

Metadata

Assignees

No one assigned

    Labels

    invalidThis doesn't seem right

    Type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions