Give a count setting its own lowest value
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 62/100
Research direction
Start from Env.Count and its existing AtMost upper bound to see how a bound is declared and how its error message is produced. Add an AtLeast(n) counterpart with its own message for values below n, leaving the zero-value message unchanged. Done when a test with a floor of 2 gets the new message for 0 and 1 rather than must stand above zero.
Written by the indexing model from the issue text.
Description
What
Env.Count takes an upper bound through AtMost, but no lower bound, so every count only has to stand above zero. Add a lower bound, such as AtLeast(n), with its own message.
Why
A setting whose lowest value is 2 answers must stand above zero for 0 and its own message for 1. Someone who fixes the first value then meets a second error. One bound gives one message for every value below the floor.
- Dominant language
- Go
- Stars
- 69
- Forks
- 3
- Avg merge
- 9h 11m
- Merged PRs (30d)
- 38
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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.
More from gopherium/framework
-
bug help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
enhancement help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
enhancement help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
enhancement help wanted
Difficulty 3/5 1-2 days Newbie friendliness 65/100
Maintainers usually reply within 1 day
-
bug help wanted
Difficulty 3/5 1-2 days Newbie friendliness 66/100
Maintainers usually reply within 1 day
All issues in gopherium/framework
Similar issues
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 61/100
Maintainers usually reply within 1 day
-
stage-fail
Difficulty 1/5 Under an hour Newbie friendliness 72/100
siyuan-note/bazaar#2405 ·
Maintainers usually reply within 1 day
-
bug priority: high workstream:cache
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
rossoctl/context-guru#707 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 73/100
prime-radiant-inc/evener#5028 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 85/100
Maintainers usually reply within 1 day