You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It could be implemented similarly to what is suggested in #8
{myField: {name:"My Field",optional: true}
Why?
In a use case where the github-project is used with multiple projects, I would like to set some fields, but only if they are present in the project. If any of these "optional" fields are not present, no error should be thrown, instead an info message should be logged via octokit.log.info
Alternatives you tried
I can't think of a simple alternative way. The existing fields would need to be loaded without using github-project, so we know the existing fields at the time of initialization. And we would need to filter out non-present fields each time we set them.
Would you be interested in contributing the feature?
yes
The text was updated successfully, but these errors were encountered:
Please avoid duplicates
What’s missing?
The ability to define some fields as optional.
It could be implemented similarly to what is suggested in #8
Why?
In a use case where the
github-project
is used with multiple projects, I would like to set some fields, but only if they are present in the project. If any of these "optional" fields are not present, no error should be thrown, instead an info message should be logged viaoctokit.log.info
Alternatives you tried
I can't think of a simple alternative way. The existing fields would need to be loaded without using
github-project
, so we know the existing fields at the time of initialization. And we would need to filter out non-present fields each time we set them.Would you be interested in contributing the feature?
The text was updated successfully, but these errors were encountered: