practicalli / practicalli/clojure-web-services
Component lifecycle overview
Open
Nobody has claimed this yet.
component lifecycle
- Dominant language
- Markdown
- Stars
- 16
- Forks
- 14
- PR merge metrics
- No merged PRs in 30d
Description
Why use one?
- reloaded repl workflow
- load components at runtime (dependency injection idiom)
Reloaded REPL workflow
- examples
Load components
- start internal services (cache, web server, embedded dB)
- populate data stores (atoms for shared state, database migrations (if short time to process))
Examples
- without component
- component
- mount
- integrant
- integrant REPL
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 file or documentation entry point is named. Start by reviewing the repository's existing documentation structure and the issue outline, then cover the REPL workflow, runtime service loading, and the listed examples; done means these topics are documented with examples for each requested approach.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- clojure
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100