dry-python / dry-python/rests

Motivation and goals?

Open
#1 1 comment 0 reactions 0 assignees View on GitHub
Dominant language
No language data
Stars
10
Forks
0
PR merge metrics
No merged PRs in 30d

Description

👋 Hi there again!

@sobolevn what are your thoughts with this library? What are the (non)goals and motivation?

So far I can see 'framework-less'. I'm also assuming it'd be according to FP principles (immutability, composability, purity)? Something like Scala's http4s? Is there something specific about REST vs generic HTTP APIs that you want to focus on? What do you see in current web frameworks that you don't like?

I could imagine the library would be centered around composing `Request -> Response` pipelines. This requires composable, functional blocks for:
- routing
- parsing/validation
- encoding/decoding (e.g. JSON)
- testing
- 'middleware'
- plugging into existing frameworks (so you can start using `rests` in your current flask/django/(a)wsgi/etc project immediately)
- dealing with DBs in a pure way

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.