Skip to content

Reject nonexistent fields in pset create #30

@schoen

Description

@schoen

Currently, hal-simplicity simplicity pset create will accept spurious field names in an input. You can just make up any field name in the JSON, and it won't raise an error. This appears to be wrong.

Interestingly, the problem seems slightly different for outputs; some spurious values may cause the entire PSET to be null (without a specific error message).

Ideally, both inputs and output arguments should be validated to catch errors early.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions