High-level API
Nobody has claimed this yet.
- Dominant language
- Erlang
- Stars
- 105
- Forks
- 34
- Avg merge
- 1d 4h
- Merged PRs (30d)
- 6
Description
In #26 we made the API lower level, exposing HTTP details, and unsurprisingly we received some feedback that it's leaky: https://github.com/aseigo/hexagon/commit/5991766b0db980acf1a0da1fab95d34046b18967#commitcomment-30019283 (thanks @aseigo!)
This issue is to collect more feedback and see if and how we want to tackle this.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading issue #26 and the linked commit discussion, then review the 14-comment thread for the feedback about exposed HTTP details. Done means the project has an agreed direction and scope for whether and how to provide a higher-level API; this issue does not name files, tests, or an implementation entry point.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- erlang
- Domain
- api, backend-api-design
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 18/100