Environment

• Elixir version (elixir -v): Erlang/OTP 23 [erts-11.2] [source] [64-bit] [smp:12:12] [ds:12:12:10] [async-threads:1] [hipe]
• Absinthe version (mix deps | grep absinthe): absinthe 1.6.4 / absinthe_plug 1.5.8
• Client Framework and version (Relay, Apollo, etc): graphiql

Expected behavior

Changing my types file from field(:id, :id) to field :id, :string do resolve(fn object, _, _ -> {:ok, GlobalId.encode(Spiff.Comment, object.id)} end) end

Sometimes does not register as a change

Actual behavior

id continued to behave as a plain db column until I ran mix clean and restarted. Then it works as expected. Restarting iex on its own is not enough to break the stale cache.

We observe the same behavior and even worse: turning context_id: "global" made messages from adjacent topics leak to the users who weren't subscribed.

These changes look good! Will look at doing a release shortly.

This adds support for defining open_ended scalars that can recieve arbitrary GQL data. We opted to put this behavior behind a flag so that it is an opt-in feature. This was a necessary feature to support the Federation spec's _Any scalar

Once this merges can we release it as an RC? I would like to get the absinthe_federation library on hex but it will depend on these changes. I would also like to submit a talk proposal to Elixir conf to talk about federation and those submissions are due July 11th, 2021

Thanks!

This was mysterious to me until I poked around the code a little.

Thanks!

<!--

Precheck

Thank you for submitting a pull request! Absinthe is a large project, and we really appreciate your help improving it.

Please keep the following in mind as you submit your code; it will help us review, discuss, and merge your PR as quickly as possible.

• Tests are good! Please include them if possible.
• Documentation is good:
  • Modules should have a @moduledoc (may be false)
  • Public functions should have a @doc (may be false)
  • Consider checking /guides for documentation that needs to be updated
• Specifications are good. Include @spec when possible.
• Good Git history behavior is good. Don't rebase your PR branch, and make small, focused commits. We generally squash commits on merge for you, unless there is a reason not to (multiple committers on a PR, etc).
• Matching existing code style is good.

We're happy to work with you, providing guidance and assistance where we can, collaborating with you to help your contribution become part of Absinthe. Thanks again!

As always, feel free to reach out for questions/discussion via:

• Our Slack channel (#absinthe-graphql): https://elixir-slackin.herokuapp.com
• The Elixir Forum: https://elixirforum.com

-->

<!--

Precheck

Thank you for submitting a pull request! Absinthe is a large project, and we really appreciate your help improving it.

Please keep the following in mind as you submit your code; it will help us review, discuss, and merge your PR as quickly as possible.

• Tests are good! Please include them if possible.
• Documentation is good:
  • Modules should have a @moduledoc (may be false)
  • Public functions should have a @doc (may be false)
  • Consider checking /guides for documentation that needs to be updated
• Specifications are good. Include @spec when possible.
• Good Git history behavior is good. Don't rebase your PR branch, and make small, focused commits. We generally squash commits on merge for you, unless there is a reason not to (multiple committers on a PR, etc).
• Matching existing code style is good.

We're happy to work with you, providing guidance and assistance where we can, collaborating with you to help your contribution become part of Absinthe. Thanks again!

As always, feel free to reach out for questions/discussion via:

• Our Slack channel (#absinthe-graphql): https://elixir-slackin.herokuapp.com
• The Elixir Forum: https://elixirforum.com

-->

Apollo federation is not built in, but I don't see anything standing in the way of someone writing a library that enabled it on top of Absinthe. At this point Absinthe has exposed 100% complete control over how schemas are built, when schemas are built, and how queries are executed.

So is it not possible to leverage Apollo Federation while also using Absinthe Elixir ?

Mesh should, at least in principle, be able to add a Federation implementation to an existing nonconforming schema: https://www.graphql-mesh.com/docs/transforms/federation via https://github.com/0xR/graphql-transform-federation

@d-led Schema stitching and federation are not the same though

Each system has a unique strategy for combining sub-services:

- Federation services are aware of each other’s data while the gateway is a generic agent that combines them. The gateway configures itself by reading SDLs from each service, and may be reloaded on the fly with new SDLs.

- Stitching services remain unaware of each other while the gateway loads and combines their schemas. Recent development has added SDL annotations that allow stitched schemas to also be reloaded on the fly.

So is it not possible to leverage Apollo Federation while also using Absinthe Elixir ?

If submitting a bug, please provide the following:

Environment

• Elixir version (elixir -v):

Erlang/OTP 23 [erts-11.2] [source] [64-bit] [smp:16:16] [ds:16:16:10] [async-threads:1] [hipe]

Elixir 1.11.4 (compiled with Erlang/OTP 23)

• Absinthe version (mix deps | grep absinthe): 1.6.3
• Client Framework and version (Relay, Apollo, etc): Not relevant as it's a backend bug

Expected behavior

Define an enum type with the shorthand syntax:

enum :example_type, values: [:A, :B, :C]

In the schema, have a field with default value: arg :example, :example_type, default_value: :A.

It should work as expected.

Actual behavior

A compilation error is thrown:

(ArgumentError) you attempted to apply :value on [:A, :B, :C]. If you are using apply/3, make sure the module is an atom. If you are using the dot syntax, such as map.field or module.function(), make sure the left side of the dot is an atom or a map
    :erlang.apply([:A, :B, :C], :value, [])
Stacktrace:
  │ (absinthe 1.6.3) lib/absinthe/phase/schema/validation/default_enum_value_present.ex:33: anonymous fn/1 in Absinthe.Phase.Schema.Validation.DefaultEnumValuePresent.validate_defaults/2
  │ (elixir 1.11.4) lib/enum.ex:1411: Enum."-map/2-lists^map/1-0-"/2
  │ (absinthe 1.6.3) lib/absinthe/phase/schema/validation/default_enum_value_present.ex:33: Absinthe.Phase.Schema.Validation.DefaultEnumValuePresent.validate_defaults/2
  │ (absinthe 1.6.3) lib/absinthe/blueprint/transform.ex:16: anonymous fn/3 in Absinthe.Blueprint.Transform.prewalk/2
  │ (absinthe 1.6.3) lib/absinthe/blueprint/transform.ex:109: Absinthe.Blueprint.Transform.walk/4
  │ (elixir 1.11.4) lib/enum.ex:1533: Enum."-map_reduce/3-lists^mapfoldl/2-0-"/3
  │ (absinthe 1.6.3) lib/absinthe/blueprint/transform.ex:145: anonymous

I had to change the definition of the enum type like this:

  enum :example_type do
    value :A
    value :B
    value :C
  end

for it to work, even though it seems that they should mean the exact same thing.

Bumps credo from 1.5.1 to 1.5.5. <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/rrrene/credo/blob/master/CHANGELOG.md">credo's changelog</a>.</em></p> <blockquote> <h1>Changelog</h1> <h2>1.6.0</h2> <ul> <li>...</li> </ul> <h3>Exit Status</h3> <ul> <li>Credo succeeds with an exit status of 0 (like any other program).</li> <li>Credo fails with an exit status between 1 and 127 if it shows any issues.</li> <li>Exit statuses above or equal to 128 indicate an actual runtime error during analysis itself.</li> </ul> <h3>New checks</h3> <ul> <li><code>Credo.Check.Design.SkipTestWithoutComment</code></li> <li><code>Credo.Check.Readability.PipeIntoAnonymousFunctions</code></li> <li><code>Credo.Check.Refactor.MapJoin</code></li> </ul> <h2>1.5.4</h2> <ul> <li>Fix bug where <code>:exit_status</code> was not a valid option for <code>use Credo.Check</code></li> <li>Fix bug where <code>mix credo diff</code> exited with a non-zero exit status even if no issues were shown</li> <li><code>mix credo diff</code> now fails with an error if the given <code>ref</code> was not found</li> </ul> <h2>1.5.3</h2> <ul> <li>Fix bug in <code>diff</code> and <code>version</code> command when <code>git</code> is not installed</li> </ul> <h2>1.5.2</h2> <ul> <li>Fix output bug in <code>diff</code> command</li> <li>Fix bug in <code>diff</code> command when run on a Git ref that does not contain a given <code>--config-name</code></li> <li>Fix bug in all commands when a given <code>--config-name</code> is not found</li> <li>Fix false positive in <code>Credo.Check.Warning.ExpensiveEmptyEnumCheck</code></li> <li>Fix false positive in <code>Credo.Check.Refactor.PipeChainStart</code> regarding custom operators</li> <li>Fix <code>--version</code> to include pre version and build info for unpublished versions (e.g. when the dep is included via <code>path:</code> or <code>github:</code>)</li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li>See full diff in <a href="https://github.com/rrrene/credo/commits">compare view</a></li> </ul> </details> <br />

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

<details> <summary>Dependabot commands and options</summary> <br />

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
• @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
• @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
• @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
• @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language
• @dependabot badge me will comment on this PR with code to add a "Dependabot enabled" badge to your readme

Additionally, you can set the following in your Dependabot dashboard:

• Update frequency (including time of day and day of week)
• Pull request limits (per update run and/or open at any time)
• Automerge options (never/patch/minor, and dev/runtime dependencies)
• Out-of-range updates (receive only lockfile updates, if desired)
• Security updates (receive only security updates, if desired)

</details>

Superseded by #175.

Bumps credo from 1.5.1 to 1.5.6. <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/rrrene/credo/blob/v1.5.6/CHANGELOG.md">credo's changelog</a>.</em></p> <blockquote> <h2>1.5.6</h2> <ul> <li>Ensure compatibility with Elixir 1.12</li> </ul> <h2>1.5.5</h2> <ul> <li>Fix bug where compilation warnings are shown if compilation directory is not part of a Git work tree</li> <li>Fix bug in <code>mix credo diff</code> where too many issues are reported because</li> </ul> <h2>1.5.4</h2> <ul> <li>Fix bug where <code>:exit_status</code> was not a valid option for <code>use Credo.Check</code></li> <li>Fix bug where <code>mix credo diff</code> exited with a non-zero exit status even if no issues were shown</li> <li><code>mix credo diff</code> now fails with an error if the given <code>ref</code> was not found</li> </ul> <h2>1.5.3</h2> <ul> <li>Fix bug in <code>diff</code> and <code>version</code> command when <code>git</code> is not installed</li> </ul> <h2>1.5.2</h2> <ul> <li>Fix output bug in <code>diff</code> command</li> <li>Fix bug in <code>diff</code> command when run on a Git ref that does not contain a given <code>--config-name</code></li> <li>Fix bug in all commands when a given <code>--config-name</code> is not found</li> <li>Fix false positive in <code>Credo.Check.Warning.ExpensiveEmptyEnumCheck</code></li> <li>Fix false positive in <code>Credo.Check.Refactor.PipeChainStart</code> regarding custom operators</li> <li>Fix <code>--version</code> to include pre version and build info for unpublished versions (e.g. when the dep is included via <code>path:</code> or <code>github:</code>)</li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/rrrene/credo/commit/9bee6e0a2bb46ff809375555742d0ad8590cb913"><code>9bee6e0</code></a> Bump version to 1.5.6</li> <li><a href="https://github.com/rrrene/credo/commit/62b12d2209f5e13a73e4f85b849acba2c5010fe2"><code>62b12d2</code></a> Update CHANGELOG</li> <li><a href="https://github.com/rrrene/credo/commit/01578e456a7d2f1cee496731f306167ae2ddbc22"><code>01578e4</code></a> Fix tests for Elixir versions < 1.12</li> <li><a href="https://github.com/rrrene/credo/commit/30fab358ec6bb1ffe05d8472c440d7dd8be72b98"><code>30fab35</code></a> Update CI to use erlef/setup-beam</li> <li><a href="https://github.com/rrrene/credo/commit/be5c628c5ebaa5e9b09c896cbcb1400fd0e53089"><code>be5c628</code></a> Fix interpolation helper for Elixir 1.12</li> <li><a href="https://github.com/rrrene/credo/commit/bd56b1241a6d5affe3064039aba1ae444c1fda3d"><code>bd56b12</code></a> Fix space around operators check</li> <li><a href="https://github.com/rrrene/credo/commit/4cceec0a7447601011933bc378b87d512a66045e"><code>4cceec0</code></a> Use Elixir 1.12.0-rc.0</li> <li><a href="https://github.com/rrrene/credo/commit/364775092c2b96ff4e33adff087df9cd224e3c36"><code>3647750</code></a> Bump version to 1.5.5</li> <li><a href="https://github.com/rrrene/credo/commit/6d9aeb5cf808ceaff31bec35139857280940244f"><code>6d9aeb5</code></a> Update CHANGELOG</li> <li><a href="https://github.com/rrrene/credo/commit/404886ac9c4dfc732a1bd316910c6984fe7e7e31"><code>404886a</code></a> Check if cwd is a Git directory when compiling</li> <li>Additional commits viewable in <a href="https://github.com/rrrene/credo/compare/v1.5.1...v1.5.6">compare view</a></li> </ul> </details> <br />

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

<details> <summary>Dependabot commands and options</summary> <br />

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
• @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
• @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
• @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
• @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language
• @dependabot badge me will comment on this PR with code to add a "Dependabot enabled" badge to your readme

Additionally, you can set the following in your Dependabot dashboard:

• Update frequency (including time of day and day of week)
• Pull request limits (per update run and/or open at any time)
• Automerge options (never/patch/minor, and dev/runtime dependencies)
• Out-of-range updates (receive only lockfile updates, if desired)
• Security updates (receive only security updates, if desired)

</details>