Skip to content

Allow custom fields to be optional  #312

Description

@Seraf

Hello,

We are using custom fields to link a pull request number, or link a pull request as a dependency.
An example of a dependency could be a PR number of the API which lives in another repository.

We are currently using a string to pass an empty value "" but ideally, we would like to use the int type, and be able to specify an optional parameter on the field.
This would allow to not have this empty field in the fragment, and avoid templating errors if an optional field doesn't exist in the fragment.

I guess that some other use-cases may exists for optional fields :-)

Do you think it makes sense?

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

enhancementNew feature or request

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions