Maarten van Vliet

> I didn't want to open a new issue since this one covers it. If we add duplicate directives for a field like `@deprecate` or `@tag`, it will break the...

There has been a release for the go client :) https://github.com/netlify/open-api/pull/170#issuecomment-566112522

I can see value in that for some use cases. Instead of the context I think it makes more sense to pass through the resolution struct just like normal resolver...

I could not reproduce this. Do you have a step by step guide on getting this error?

Agreed with @gemantzu, using proper slugs would be preferable. There's no uniqueness enforced on company name either, so if we have duplicates they would result in unreachable urls.

I'd like to tackle the "remote" option for companies. I suggest adding a remote true/false field to the companies table. Or are more options needed? Also, what should the design...

Yes that would be helpful, I do some quick checks usually to check the claim (blogs, jobs, github repo's, phoenix html tags, cowboy http headers) but having submissions provide evidence...

I have couple of ideas: * Add company logo Either direct image url or upload to s3 * Twitter feed of companies Much like https://elixirstatus.com/ does, when companies are created...

yes. done :)

You can look into the tests for examples on how it works: https://github.com/absinthe-graphql/absinthe/blob/master/test/absinthe/schema/notation/experimental/import_sdl_test.exs There are also some examples here: https://github.com/newrelic/absinthe-schema-stitching-example/blob/master/apps/soccer_team_app/lib/soccer_team_app/schema.ex