Sindre Røkenes Myren

Possible work-around for now: If you always set the field in your hook on insert/update (or remove it from the payload if present when `ttl` is 0), any value the...

The link you posted is extremely useful @Dragomir-Ivanov. > The thing is that sub-resource etags aren't current's one and an etag is associated with a specific path+query-string, so it should...

Btw, this is defiantly in the enchantment category. The main goal of supporting it would be out of correctness and _browser_ compatibility - if this is something that a lot...

Ah, ok so `Field.Schema` is the initial support for sub-schemas here. I actually like the `Object` `FieldValidator` better than having `Field.Schema`, as it's both more consistent, and avoids ambiguous meaning...

> For #65 I would rather wait for the Go official way to handle that. OK, for the manifest part, but tagging a release in Git (e.g. v0.1.0), is something...

@rs - updated the title & description.

I don't know if I can/want to figure out the implications on reference checking... there are some other easier issues I would rather look at, e.g. JSON schema ones...

At least not know

@rs Looking at the definition of Object: ``` type Object struct { Schema *Schema } ``` Could we not make Schema implement FieldValidator or at least change the definition to:...

Maybe it's not so easy btw. At least not without introducing _additional_ breaking changes everywhere... It would be _nice_ to make the API consistent by removing the Schema attribute, while...