ring-clojure / ring-clojure/ring
Strange ring-reload interaction causes it to detect false cyclic ns dependencies
Open
Nobody has claimed this yet.
- Dominant language
- Clojure
- Stars
- 3.9k
- Forks
- 528
- PR merge metrics
- No merged PRs in 30d
Description
A user of spiral has encountered this strange issue: dgrnbrg/spiral#19 Do you have any insight as to what could be the difference between the two? Could it be an interaction with core.async?
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 reading the linked dgrnbrg/spiral#19 report and compare the two behaviors described there. Investigate whether ring-reload interacts with core.async and cyclic namespace detection; done means reproducing the false dependency report and identifying its cause or documenting why the cases differ.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- clojure
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100