Tristan Zajonc

This is fixed, see: https://github.com/tgriesser/checkit/blob/3625964e0154f41630bb44b6a9eae417a575bae1/test/spec.js#L299

@alexeagle I think you'll still run into problem supporting both yarn workspaces (e.g. for interactive development with livereload) and Bazel. To support a local yarn install, you need the subpackages...

I believe FB just returns null for fields that you do not have permission to. Having multiple type systems with fine grained permissions will make code generation, relay, type checking,...

Right, but this shouldn't be a schema concern. For code generation, relay, and type checking to work, the schema can't rely on runtime attributes generating new schemas. The schema should...

@KyleAMathews Absolutely. In that case I think the solution is multiple endpoints. Have a flag for your new secret release and return a different schema if that flag is present....

One alternative is https://github.com/kumailht/responsive-elements.

I wasn't sure about the use case for same origin support with `url` source even on browsers that support sandbox attribute. In the example, `http://example.com/profile_viewer.html` can presumably be accessed directly,...

@tarcieri that's my understanding. The problem is that the insecure content is almost always accessible directly as well, which makes same-domain sandbox not so useful. All you need is for...

This is documented in the readme, but I agree it would be nice to try to have a mapping. These become query parameters, so you'll need to define a mapping...

This seems to document a bug in the upstream lance with limit + offset, but I have been able to look at it closely.