Ben Wilson

The issue is that schemas are not tied to a single adapter at the moment. Adapters are set as an option on the plug, or wherever the schema is actually...

because of how `Macro.underscore` works the following is already possible: ``` defmodule Schema do use Absinthe.Schema query do field :foo_bar, type: :string do resolve fn _, _ -> {:ok, "hello"}...

Right yeah I think we also just need to make sure the documentation on Adapters is up to date. The whole point of the Adapter system is so that schemas...

Thank you so much for creating an example! I will look into this today.

Ah, this is by far the most succinct description of the issue, thanks for doing this. Let me look into this this weekend.

Hey folks, Thanks for offering a PR! This is all going to be reworked as part of the Absinthe 1.5 schema update. We'll be providing some docs on what to...

@alanpeabody is this a blocker there? Adapters should provide everything you need there. There are some consistency issues when trying to use the built in adapter with specific field names...

@iautom8things keep in mind that nothing requires that you use the same graphql field names as your database column names. In fact you can even rename them at the ecto...

> But this creates a possibility for a race-condition Yeah this will almost assuredly race because the end client hasn't even subscribed to the actual pubsub topic over which they'll...

Right, so the main challenges to solve are: How are subscription topics mapped to presence topics?