akira/exq 1263
Job processing library for Elixir - compatible with Resque / Sidekiq
benwilson512/ar-transmogrifier 6
Convert your ActiveRecord schema.rb into Ecto Models.
A curated list of amazingly awesome Elixir and Erlang libraries, resources and shiny things. Updates:
benwilson512/absinthe_benchmark 0
super basic code to profile absinthe with
Mnesia wrapper for Elixir.
benwilson512/apollo-tracing-elixir 0
Apollo Tracing middleware for Absinthe
pull request commentabsinthe-graphql/absinthe
Yes, this will be supported.
comment created time in 3 days
push eventabsinthe-graphql/absinthe
commit sha bdb0531aed1f0336a6844a63b43095acd0777277
Fix typos in the documentation (#1101)
push time in 8 days
pull request commentabsinthe-graphql/absinthe
Fix typos in the documentation
Thanks!
comment created time in 8 days
issue commentabsinthe-graphql/absinthe_phoenix
Has anyone been able to reproduce this issue in a locally running application? That might simplify testing any proposed fixes here.
comment created time in 9 days
pull request commentabsinthe-graphql/absinthe
Use makeup_graphql to get GraphQL syntax highlighting in docs
Thank you!
comment created time in 14 days
push eventabsinthe-graphql/absinthe
commit sha 50bbaae409c6c67e69c69a6cf1d28427c00ed897
Use makeup_graphql to get GraphQL syntax highlighting in docs (#1099) Co-authored-by: Nick Hallstrom <nick.hallstrom@divvypay.com>
push time in 14 days
PR merged absinthe-graphql/absinthe
Docs before:
Docs after:
pr closed time in 14 days
issue closedabsinthe-graphql/absinthe
Unable to conditionally define an enum value
Environment
- Elixir version:
Erlang/OTP 24 [erts-12.0.3] [source] [64-bit] [smp:6:6] [ds:6:6:10] [async-threads:1] [jit]
Elixir 1.12.2 (compiled with Erlang/OTP 22)
- Absinthe version: 1.6.4
Expected behavior
I tried to define an enum value, that is only available during testing, but I was also able to use it during development.
Actual behavior
The enum value was available during development
Relevant Schema/Middleware Code
enum :social_media do
value :google
value :facebook
value :twitter
value :linkedin
if Mix.env() == :test do
value :mock
end
end
closed time in 14 days
Awlexus
issue commentabsinthe-graphql/absinthe
Unable to conditionally define an enum value
This isn't really possible for us to support as written. Your best bet is to do:
if Mix.env() == :test do
enum :social_media do
value :google
value :facebook
value :twitter
value :linkedin
value :mock
end
else
enum :social_media do
value :google
value :facebook
value :twitter
value :linkedin
end
end
Or you can use a pipeline modifier: https://hexdocs.pm/absinthe/Absinthe.Schema.html#module-custom-schema-manipulation-in-progress
comment created time in 14 days
pull request commentabsinthe-graphql/absinthe
Use makeup_graphql to get GraphQL syntax highlighting in docs
Very cool! What remains to take this beyond draft?
comment created time in 16 days
pull request commentabsinthe-graphql/absinthe_phoenix
v2.0.2 has been published.
comment created time in 16 days
push eventabsinthe-graphql/absinthe_phoenix
commit sha 2fcf0631e568887d46a0e778dcc9cc05897ecae2
version bump
push time in 16 days
pull request commentabsinthe-graphql/absinthe
Add failing test for macro deprecated field in SDL render
@ymtszw that forum post is out of date. Absinthe does support calling directives in SDL.
see: https://github.com/absinthe-graphql/absinthe/blob/master/test/absinthe/schema/notation/experimental/import_sdl_test.exs#L567-L592
comment created time in 24 days
push eventabsinthe-graphql/dataloader
commit sha 7900c19927ca262036ce7664e1afbd6c8dbf8ec3
Update telemetry dependency to stable ~> 1.0
commit sha e58892454dfe59e4f229b11f2ed8c9b9c704c4ac
Update mix.exs
commit sha 91db9e4f3cb8e3b375c997d83e4b1f57f97e3bf7
Merge pull request #132 from bmuller/update-telemetry-dependency Update telemetry dependency to stable ~> 1.0
push time in 24 days
PR merged absinthe-graphql/dataloader
There were no changes in the Telemetry 1.0.0 release - but it does represent the first "stable" version of the API.
pr closed time in 24 days
push eventbmuller/dataloader
commit sha e58892454dfe59e4f229b11f2ed8c9b9c704c4ac
Update mix.exs
push time in 24 days
Pull request review commentabsinthe-graphql/dataloader
Update telemetry dependency to stable ~> 1.0
defmodule Dataloader.Mixfile do defp deps do [- {:telemetry, "~> 0.4"},+ {:telemetry, "~> 1.0"},
{:telemetry, "~> 1.0 or ~> 0.4"},
comment created time in 24 days
issue closedabsinthe-graphql/dataloader
Hi all,
we were just wondering if a new release is planned that includes all features and fixes that have been merged since 1.0.8 from August 2020. We rely on some of our contributions and others and I'd be great to have a specific version locked again instead of pointing to master.
Thanks!
closed time in a month
follmann
push eventabsinthe-graphql/dataloader
commit sha a515f322513b6489171d4064c253a9ea11d946f3
mix version fixes
push time in a month
push eventabsinthe-graphql/dataloader
commit sha 2e010dbb900ecfcc9f546b52df53650c8212525e
doc update
push time in a month
push eventabsinthe-graphql/dataloader
commit sha 0cbaf0ab0a6f508b286c4913f2a6ba9e32ca3e58
version bump
push time in a month
Pull request review commentabsinthe-graphql/dataloader
Fix Ecto sandbox when using Ecto.Multi
+defmodule Dataloader.Ecto.MultiSyncTest do+ use ExUnit.Case, async: false++ alias Dataloader.User+ alias Dataloader.TestRepo, as: Repo++ setup do+ :ok = Ecto.Adapters.SQL.Sandbox.checkout(Repo)+ :ok = Ecto.Adapters.SQL.Sandbox.mode(Repo, {:shared, self()})++ test_pid = self()++ source =+ Dataloader.Ecto.new(+ Repo,+ query: &query(&1, &2, test_pid)+ )++ loader =+ Dataloader.new()+ |> Dataloader.add_source(Test, source)++ {:ok, loader: loader}+ end++ defp query(schema, _params, test_pid) do+ send(test_pid, :querying)++ schema+ end++ test "loads data", %{loader: loader} do+ user =+ %User{username: "Ben Wilson"}+ |> Repo.insert!()++ result =+ Ecto.Multi.new()+ |> Ecto.Multi.run(:loader, fn _, _ ->+ loader+ |> Dataloader.load(Test, User, user.id)+ |> Dataloader.run()
All of the errors actually show that the error is that this isn't returning an :ok tuple. If you fix that issue do the other issues persist?
comment created time in a month