dry-python / dry-python/rests

Motivation and goals?

Ouverte
#1 1 commentaire 0 réactions 0 personnes assignées Voir sur GitHub
Langage dominant
Aucune donnée de langage
Étoiles
10
Forks
0
Métriques de merge des PR
Aucune PR mergée en 30 j

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

Guide de contribution

Aucun guide de contribution indexé pour ce dépôt

Évaluation

Cette issue n'a pas encore été évaluée.

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.