`namespace` not only for tasks, but also for functions hermetization
Nobody has claimed this yet.
- Dominant language
- Ruby
- Stars
- 2.5k
- Forks
- 650
- Avg merge
- 6m
- Merged PRs (30d)
- 3
Description
It's a known fact, that ruby function defined in a namespace will be defined in a global scope rather than inside of a hermetized context. So ruby function defined in one namespace will be visible in another and it may be unintentionally overridden.
It would be nice if namespace could be a context for ruby functions as well as rake tasks.
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 reproducing the issue with Ruby functions defined in two separate namespace blocks and confirm that one can be visible from or override the other. Then trace how Rake handles namespace context for tasks and determine the equivalent behavior needed for functions. Done means functions defined in one namespace are hermetized from other namespaces without breaking existing task behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ruby
- Domain
- build-system
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100