separate lib for CatQueue

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

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
24/100
Issue type
Refactor
Clarity
Needs clarification
Activity status
Stale
Domain
backend

Research direction

Start by reading the CatQueue implementation and the repository’s package structure to identify what would need to move into a separate library. The issue gives no file paths, tests, or acceptance criteria; clarify the intended library boundary and integration before making changes.

Written by the indexing model from the issue text.

Description

status: needs more info

There seems to be nothing particularly "Catty" about CatQueue. Perhaps, with the additional PRs I've made, it could live in its own lib, and get pulled in here?

Dominant language
PureScript
Stars
22
Forks
11
Avg merge
2d 23h
Merged PRs (30d)
1

Getting set up

  • No Dockerfile or Docker Compose file
  • Has a pull request template
  • No 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.

More from purescript/purescript-catenable-lists

All issues in purescript/purescript-catenable-lists

Similar issues

More Backend & API Design issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.