dry-python / dry-python/rests

Motivation and goals?

未关闭
#1 1 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看
主要语言
没有语言数据
星标
10
派生
0
PR 合并指标
30 天内没有已合并 PR

描述

👋 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

贡献指南

这个仓库没有索引到贡献指南

评估

这个 Issue 还没有评估数据。

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。