Do better analysis

Open
#15 0 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
20/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
clojure
Domain
tooling

Research direction

Start by reading Clerk and tools.analyzer, the examples named in the issue, to understand how Clerk analyzes Clojure files and gathers data. Compare those techniques with the analyzer's purpose of analyzing user submissions. The issue does not define an entry point, files, tests, or a concrete completion condition.

Written by the indexing model from the issue text.

Description

Clerk was just open sourced today and I am very excited. Nextjournal has been doing amazing things and I've taken much inspiration from their work, we seem to have the same taste in tooling. They provide a next-generation coding notebook experience, and have previously open-sourced clojure-mode for Codemirror 6 which I'd love to integrate into our web editor as well... but that's another issue.

The reason I'm so excited about Clerk is that it makes wonderful use of tools.analyzer, and I tend to work best when given good examples to follow. The techniques they use to analyze Clojure files and gather comprehensive data to provide their live notebook environment will also apply to our purpose for analyzing user submissions.

Dominant language
Clojure
Stars
2
Forks
7
PR merge metrics
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

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.

More from exercism/clojure-analyzer

All issues in exercism/clojure-analyzer

Similar issues

More Clojure issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.