practicalli / practicalli/clojure

Spec projects - verify names specifications

Open
#180 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

spec
Dominant language
Makefile
Stars
117
Forks
36
PR merge metrics
No merged PRs in 30d

Description

*** TODO Check requires meet team specifications
- [ ] Ensure single character aliases are not used
- [ ] Add alias exception for cognitect spec and datomic
- [ ] Ensure names of existing clojure.core functions are not used
- [ ] Add aliases for common libraries (eg. integrant can be :ig :integrant :component :system :lifecycle)

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by locating the spec-project name and alias validation entry point; the issue does not identify a file or test. Compare the current checks with the listed requirements, including cognitect spec and datomic exceptions, clojure.core names, and common-library aliases. Done means each checklist item is implemented and covered by verification.

Written by the indexing model from the issue text.

Assessment

Tech stack
clojure
Domain
tooling
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.