lambdaisland / lambdaisland/classpath
Update from tools.deps.alpha
Nobody has claimed this yet.
- Dominant language
- Clojure
- Stars
- 90
- Forks
- 7
- PR merge metrics
- No merged PRs in 30d
Description
I don't know exactly what the deal is with tools.deps and tools.deps.alpha. My knowledge of their inner-workings is limited. But classpath is reliant on create-basis slurp-deps from tools.deps.alpha. Do you want to upgrade? If so, would you like a PR?
I only ask because I really have no idea what a prudent plan around transitioning looks like. Both functions are present and the PR wouldn't take me much time, but if updating breaks other things you've got going on or your users I don't want to bother with it. I'm using both deps and deps.alpha via a hacky deps.edn trick for the time being.
Throughout the years I've enjoyed learning with your videos, episode 32 really changed how I treated metadata. And Classpath is an important tool in my dev workflow, so... THANKS FOR THAT!
Contributor guide
No contributing guide indexed for this repository
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 tracing the classpath entry points that call tools.deps.alpha's create-basis and slurp-deps. Review the project's current dependency setup and determine whether moving to tools.deps is compatible with existing users. Done means there is an agreed transition plan and the dependency usage works without breaking current behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- clojure
- Domain
- build-system, tooling
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100