Skip to content

Indicate in the schema whether fields are optional or not #318

@Shadow53

Description

@Shadow53

I'm trying to generate a Rust client for butlerd. I've run into an issue where the schema does not make obvious whether certain fields are optional or not. The documentation may mention it, but that is not reliable to parse programmatically.

I know and appreciate that Go's "zero" values by default thing may make this difficult. I figure a good starting point would be marking all *T as optional and T as required, for actual types T. This will help me determine whether to generate the field as T or Option<T>.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions