Jake Moshenko

Plan after a recent discussion: - `LookupSubjects` becomes the exact inverse of `LookupResources` in that it - Returns all of the subjects that match the subject type of the parent...

Hi @tiev , There would be changes in `check.go`, `lookup.go`, and `expand.go`. Roughly the idea is to stop using a wrapped type that contains both results and errors on the...

in case it wasn't obvious: one is the number of milliseconds and one is the wall clock time

> Would you welcome a PR for caching marshaled bytes? I can open one for that. Load testing with a "normal" machine, e.g. one with a common proportion between CPU...

How did the load tests go? Anything interesting to report?

Maybe we could move the accurate coster into a goroutine decoupled from the serving process. It shouldn't affect latency on the read path.

I think it's more than just schema operations, I think it's also read, write, and delete, all of which can do one or more downstream requests.

EDIT: I actually think the modified proposal below is a bad idea now, since you lose the semantics of a user editing themselves, and it just makes the permission wide...

Just found the build-in graphiql support, doesn't change the issue but is a great workaround in the meantime. Thanks!

#110 added allOf support for schemas, but not for response objects directly. As an example, the PagerDuty API composes their response objects for components using allOf: ```json "/schedules": { "get":...