markbates / markbates/configatron
When `false` is set in `Configatron::Dynamic`, the call result becomes `nil`.
Open
Nobody has claimed this yet.
- Dominant language
- Ruby
- Stars
- 593
- Forks
- 74
- PR merge metrics
- No merged PRs in 30d
Description
In the current latest version (v4.5.0):
```ruby
proc = Configatron::Proc.new { false }
proc.call
=> false
dynamic = Configatron::Dynamic.new { false }
dynamic.call
=> nil
```
When the value is false, the call result differs between Proc and Dynamic.
The call result should be the same.
Contributor guide
No contributing guide indexed for this repository
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 reproducing the two examples with Configatron::Proc and Configatron::Dynamic, then compare their call implementations. Verify that a Dynamic block returning false currently produces nil and that the corrected behavior matches Configatron::Proc by returning false.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ruby
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 55/100