Sindre Røkenes Myren

I have done some background thinking on this, and I have a rather radical proposal: - Move `schema.Fields` from `Schema` to `Object`, and let the Schema have a `Validator` field...

The error type returned from `schema.Object` (and any other nested type), will be the existing `ErrorMap` type.

IN #151, I am proposing to replace `ValuesValidator FieldValidator` in `schema.Dict` with `Values Fields` and later do the same in `schema.Array`. As already proposed in this issue, `schema.Object` will also...

> I have done some background thinking on this, and I have a rather radical proposal (...) I want to drag this a _little bit_ further. I think the `schema.Field`...

I plan to start this issue by: - Creating a new (blank) repo for the schema package for experimental purposes. - Copy over just enough types to get the design...

We use rest-layer actively. We are pretty satisfied with it, but over time we have hit most of the limitations regarding the current schema package at some point, and either...

Link to proto-type for new schema design: - https://github.com/searis/schema It's not in a working state.

Just to give a solution you can use today; you _can_ use: - `filter={id:{$lt:}}`. // or `$gt`, based on ordering. - `sort=-id` // or `id` - `limit=` This can be...

Contributions are always welcome. > I found currently rest-layer provides authentication but doesn't provide authorization yet. Well, rest-layer actually [dosn't implement](https://github.com/rs/rest-layer#authentication-and-authorization) any authentication, but you are right that there are...

Sounds good.