`getBooleanInput` ignores `options.required`
Open
Nobody has claimed this yet.
bug
- Dominant language
- TypeScript
- Stars
- 5.9k
- Forks
- 1.8k
- PR merge metrics
- No merged PRs in 30d
Description
Describe the bug
- Calling
getBooleanInputto read an unset input - Calling
getBooleanInputwith{ required: false }to read an unset input throws an error
Expected behavior
getBooleanInput should function the same as getInput in the following ways:
- It respects
options.required - Inputs are not required by default
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by comparing the getBooleanInput and getInput implementations and their existing tests. Reproduce an unset input with the default options and with { required: false }, then update the behavior so both cases match the expected getInput semantics and verify the required-input case remains covered.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- api, tooling
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 45/100