lessp / lessp/fetch

Approachable by OCamlers

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

Nobody has claimed this yet.

discussion
Dominant language
Reason
Stars
52
Forks
1
PR merge metrics
No merged PRs in 30d

Description

There are different idioms in ReasonML and OCaml, camelCase vs snake_case and PascalCase vs Giraffe_case meaning that there'd be some friction if someone would like to use this in the OCaml world.

We can provide aliases, similar to what Tablecloth are doing, but that still leaves us with the status-codes being PascalCase'd.

Could also provide a separate library

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.

Research direction

Start by reviewing the naming in reason-fetch/status.rei and compare it with the alias approach used by Tablecloth. Determine whether OCaml-compatible aliases or a separate library is the intended scope, including how status codes should be exposed. Done means the chosen compatibility approach is implemented consistently across the library.

Written by the indexing model from the issue text.

Assessment

Tech stack
ocaml
Domain
api
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.