CLJS-only projects do not have a CLJ entrypoint to enable RCF macroexpansion at macroexpanion time
Open
Nobody has claimed this yet.
- Dominant language
- Clojure
- Stars
- 301
- Forks
- 14
- PR merge metrics
- No merged PRs in 30d
Description
One workaround is to use a shadow build-hook to load a CLJ namespace that sets rcf/enable!, see: https://clojurians.slack.com/archives/C7Q9GSHFV/p1688040682246669?thread_ts=1688031756.398229&cid=C7Q9GSHFV
See also #67
Example build hook: https://github.com/hyperfiddle/electric/blob/1f683adc6552be0f3f41b90e86305c6270917265/shadow-cljs.edn
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 reading the related issue #67 and the linked shadow-cljs.edn build-hook example. Determine how a CLJS-only project could provide the needed CLJ entrypoint during macroexpansion, then verify that RCF can be enabled without the documented workaround.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- clojure
- Domain
- build-system, testing
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100