Sindre Røkenes Myren

Since the scope of #77 has grown, and my progress is expected to be very slow btw. It might be good to keep this issue open, if anyone wants to...

Renamed to reflect the work that is to be done.

As a first warning, there isn't much active development of rest-layer. We for one have decided to use it more or less, as-is, and the original author, @rs, is not...

One question is if the Handler for index should handle options requests at all, or if we should have a completely different options handler. This would allow for OPTIONS requests...

If you want to add GitHub actions to this repo, here is a starting-point. If you enable GitHub Actions actions for the repo, it will, run, but at least the...

As mentioned on Slack, we at [Clarify](https://clarify.io) will be maintaining our own fork of rest-layer going forward; it just makes the development faster and easier for us to control. I...

> Why not moving the main project into an org? It does make sense to discuss this properly. I started a discussion here https://github.com/searis/rest-layer/discussions/2. It's our "selfish" view of what...

Will the md5 hashed Etag be set in the header, while the raw MD5s are made available as `_etag` in each resource? Will the original Etag be available as a...

I suppose we have three or four cases for the composite e-tag: - list view : only composite etag ("root item?") - list view with embeds : another composite etag...

Btw, making the header values e-tag of format `-` when applicable is still nice in order to make it less confusing to the user why the E-tag in the header...