luminus-framework / luminus-framework/luminus-template
An idea to introduce an explicit +calva/vscode install option
Nobody has claimed this yet.
- Dominant language
- Clojure
- Stars
- 648
- Forks
- 143
- PR merge metrics
- No merged PRs in 30d
Description
From what I see in src/leiningen/new/calva.clj .vscode folder is generated each time and there is no option to disable it.
Is there a reason to keep it this way or PR might be considered?
If this idea is approved, another PR to https://calva.io/luminus/ needs to be sent as well to mention an explicit +calva option.
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 with src/leiningen/new/calva.clj and inspect how the .vscode folder is generated in new projects. Determine the intended behavior for an explicit +calva option, then review the related documentation at https://calva.io/luminus/ if the option is approved.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- clojure, vscode
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100