thyme could use a hierarchy diagram

Open
#24 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
35/100
Issue type
Documentation
Clarity
Needs clarification
Activity status
Stale
Tech stack
haskell
Domain
documentation

Research direction

Review the supplied hierarchy diagram and compare it with the thyme type definitions. Confirm which relationships and arrowheads are incorrect or missing; done means a corrected, complete diagram is available for the project's documentation.

Written by the indexing model from the issue text.

Description

documentation

It's hard to keep track of all the different thyme types without a handy diagram. I spent some time in the same tool edwardk used for lens and produced this abomination:

diagram

There may be some incorrect bits or missing arrowheads still.

Dominant language
Haskell
Stars
47
Forks
35
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 haskell-github-trust/thyme

All issues in haskell-github-trust/thyme

Similar issues

More Haskell issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.