Generate scope subclasses with methods defined for each exposure
Open
Nobody has claimed this yet.
feature
- Dominant language
- Ruby
- Stars
- 177
- Forks
- 85
- Avg merge
- 8h 27m
- Merged PRs (30d)
- 2
Description
This would make it so that the exposures always take priority over any other methods that might be in the scope (i.e. helpers and other non-essential methods).
We should combine this with a new ReservedNameError that is raised when exposures are created with names that must not be used in order for essential functionality to be preserved.
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
No files, tests, or entry points are named. Start by locating how scopes and exposures are generated, then define tests for exposure precedence and for ReservedNameError when a reserved name is used; done means both behaviors are specified and covered.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ruby
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100