rework *enabled* accounting for CLJS compiletime/runtime
Open
Nobody has claimed this yet.
- Dominant language
- Clojure
- Stars
- 301
- Forks
- 14
- PR merge metrics
- No merged PRs in 30d
Description
- Perhaps two flags –
*erase*and*enable*(or*disable*) - Should we make everything run by default?
List of cases when we do NOT want tests to run:
- do not test on JVM REPL startup (big projects do not want to load any namespaces at all for fast REPL startup times)
- do not test during clojurescript hot code reload (JS runtime)
- do not test during clojurescript macroexpansion (JVM macroexpansion time), see #67
- tests should erase entirely in prod
There may be some other way to design the flags to achieve these behaviors. The requirement to erase tests by default perhaps can be waived if other reqs are met.
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
No file or test entry point is named. Start by tracing the current enabled accounting through the ClojureScript compiletime and runtime paths, and read the related issue #67; done means the flag design satisfies the listed REPL, hot-reload, macroexpansion, and production-erasure cases.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- clojure
- Domain
- testing
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100