Don't import elm-test as a package at route
Open
- Dominant language
- Elm
- Stars
- 42
- Forks
- 5
- PR merge metrics
- No merged PRs in 30d
Description
This issue has no description.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by locating the route that imports elm-test and inspect how the package is currently brought into the project. Confirm the intended package boundary before changing anything; done means the route no longer imports elm-test as a package and the existing test suite still passes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- elm
- Domain
- testing
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100