Josh Levinson

Allow single resource arbitrary queries to get passed as props

2

When making an arbitrary query with `connectWpQuery`, resources end up getting stored on `props.kasia.data`, even if only one resource was fetched. It'd be nice if there was a concise way...

Autodiscovery lacks documentation around CORS

2

When working with cross-origin requests, headers are only exposed when whitelisted. This means autodiscovery breaks unless a `Access-Control-Expose-Headers` header containing `Link` is sent. While this issue is not specific to...

There is currently a lot of jQuery/javascript for various browser-based actions–event handling, dom updating, dragging/dropping, autocompletion, ajax saving of data, etc. The use of a proper Backbone/Underscore app would remove...

fix: use component path to ensure edit page link works for root/index

1

In [78d6728](https://github.com/graphql/graphql.github.io/commit/78d67284635fde3fc45c7bb5425a49650ea71c89#diff-f5fdf00d27b2934559500edae0b37a71958a34e4584f097afeb95260144a761fL96), `onCreatePage` was updated to use `page.path` instead of `page.componentPath`. `page.path` is a member of the [`Page` interface](https://github.com/gatsbyjs/gatsby/blob/db41d1356c527cf4028142050978accd4abb1e9a/packages/gatsby/index.d.ts#L1779); `componentPath` is not. The value of `page.path` for the site [home...

Still maintained?

2

Hello! Great work on all this! I'm interested in using it, but am wondering if it's still in active development. Would you be responsive to PRs?