Proposal: new tag "notEmptyIfDefined" to avoid the cases when an env-var is presented but its value is an empty string
Open
- Dominant language
- Go
- Stars
- 6.3k
- Forks
- 284
- Avg merge
- 1d 17h
- Merged PRs (30d)
- 1
Description
Don't know why the tag was not request previously. I think it is pretty useful.
Contributor guide
No contributing guide indexed for this repository
Research direction
The issue names no files or tests; begin by locating the environment-tag parsing entry point and existing tag tests. Define the behavior for a present empty environment variable versus an absent one, then add the new tag and verify both cases in the relevant tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100