What useful computed properties can we provide?

[aturon]

When a value can be lazily computed by request information, it's much nicer to make that value available through the Compute trait (and Computed extractor) rather than e.g. using middleware or plumbing the Head data manually in an endpoint.

What are some examples of such values? One might be: a parsed version of the query segment. Let's generate a bunch of ideas and then implement them!

[pickfire]

Maybe we can pre-compute the ETag and Last-Modified? This might be a usecase for some API but I have yet seen some interesting implementation for this.

[aturon]

@pickfire Interesting thought! Feel free to play with this idea and open up a PR.

[tzilist]

Another one might be a passport type thing to handle different types of authentication? This may not be something worth providing out of the box from tide but certainly worth showing an example of?

[chrisabruce]

While good idea, think most frameworks leave this to middleware. Maybe a good approach would be to create a middleware piece for that. Unless we talking about common header types like basic auth?

[tzilist]

@chrisabruce agreed. I wonder if we can provide scaffolding for something like basic auth, oath, etc. But I think you are right, that should probably be middleware.

[tzilist]

We could also provide a set of tools for performing health checks?

[pickfire]

@aturon From what I looked at it, Compute are used for routes, I wonder if it could be used for middlewares for caching.

[aturon]

Closing as of #156, which eliminated the concept of "computed values".