0 comments (0 comments)1 reaction (1 reaction)0 assignees (0 assignees)Clojure1,618 stars (1,618 stars)115 forks (115 forks)batch import
good first issuehelp wantedmedium-term
Description
This issue does not include a description.
Contributor guide
- Tech stack
- None
- Domain
- testing
- Issue type
- test
- DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
- 3
- Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
- 1-3 hours
- Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
- stale
- ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
- unclear
- Prerequisites
- None
- Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
- 20
- Research direction
- The issue lacks details. First, explore the repository structure to find the test directory and understand the testing framework (likely clojure.test for Clojure or maybe dart's test package for Dart). Look for existing test files in both Clojure and Dart parts of the codebase to see conventions. Consider adding unit tests for core macros or compiler functions. Since the repo is a Clojure dialect, tests might be written in Clojure, but also check for Dart tests for Flutter integration.