practicalli / practicalli/clojure
Simple projects: clacks messenger
Nobody has claimed this yet.
- Dominant language
- Makefile
- Stars
- 117
- Forks
- 36
- PR merge metrics
- No merged PRs in 30d
Description
http://practicalli.github.io/clojure/simple-projects/encode-decode/clacks.html
- add unit tests
Update page to ask questions and then show thinking. eg. How should the light pattern be represented? How to convert between English message and light pattern?
Add link to section on pure functions,
https://github.com/jr0cket/htt-clacks
https://github.com/jr0cket/clacks-messenger - fork of original projects
Use code from that project to discuss design of data:
- keywords are very useful as hash-map keys, except when there are not great for representing data used for a key, eg cant have a keyword for a space (although you could use
:-or:SPC
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
Start with the clacks messenger page and review the linked jr0cket/htt-clacks and jr0cket/clacks-messenger projects. Add unit tests, revise the page to ask design questions before showing the reasoning, link the pure-functions section, and explain the data representation choices described in the issue. Done means the page and tests cover the requested discussion and examples.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- clojure
- Domain
- documentation, testing
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100