practicalli / practicalli/clojure
Clojure tools.deps and development environments (dev, test, prod)
Nobody has claimed this yet.
- Dominant language
- Makefile
- Stars
- 117
- Forks
- 36
- PR merge metrics
- No merged PRs in 30d
Description
From slack
https://clojurians.slack.com/archives/C6QH853H8/p1592263545342600
We have a monorepo at work and we specifically use CLJ_CONFIG to set the "user" deps.edn to come from a specific directory in the monorepo so that we have a single, central place for all repo-wide aliases anyone needs. This also helps maintain repeatability because each developer's "user" deps.edn is excluded and we can control exactly what each alias does.
if subprojects have paths that are loaded based on alias, do you configure this all in the central deps.edn instead?e.g {:extra-paths ["subproject1/test" "subproject2/test"]}
It depends on whether the alias (and the optional subproject) are going to be needed for "all" other subprojects or just specific one(s). We scope things appropriately.
All our subprojects are at the same level so ../subproject/path always works.
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 repository files, tests, or entry points are named. Start by reading the linked Slack discussion and reviewing how this project documents tools.deps, CLJ_CONFIG, and central deps.edn aliases. This needs a defined documentation scope and acceptance criteria before completion can be assessed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- clojure
- Domain
- cli, tooling
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100