Glyph

Klein routers share too much state between class- and instance-level copies

6

A use-case to set the stage: I want to generalize my approach to `handle_errors` and sub-routes. This means I want to do something like: ``` @attr.s class RootAPI: remoteErrorHandlerConfig =...

Following up on #174 : https://github.com/twisted/klein/pull/174#discussion_r108026332

MIME, someday, maybe*

2

In a properly REST application, the server should engage in [content negotiation](https://en.wikipedia.org/wiki/Content_negotiation) to deliver the client's preferred representation of a resource. I would love to make it possible, within klein,...

Use-case: we have a list of things which have a display name, an interesting attribute, and an internal ID. We want to render something like `display nameinteresting attribute` for each...

☂ general awesomeness for klein.Plating

1

Here are some things that should be added to klein.Plating to make it really complete, which were left out of the initial implementation (#118) to keep it compact: - [...

There are two parts to this, although this is one ticket because I don't think they can be handled separately: 1. JSON serialization for attr.s-ified objects 2. slot-filling for attr.s-ified...

It should be possible to render a supported type (such as a number) in a different way (such as a roman numeral).

datetime rendering for klein.Plating

1

They should be serialized for both JSON and HTML; custom renderer in HTML, extension of 'default' hook in JSON.

The original prototype in #89 referred to multiple different loader types, and the initial implementation in #118 .