graphql-erlang
graphql-erlang copied to clipboard
jlouis
GraphQL implementation in Erlang.
It currently displays a warning ``` Warning: ambiguous call of overridden auto-imported BIF alias/1 - use erlang:alias/1 or "-compile({no_auto_import,[alias/1]})." to resolve name clash % 312| orddict:append(alias(S), S, Grouped)); ```
See #215 Spec http://spec.graphql.org/October2021/#sec-Boolean
Hello Jesper, First of all - Thanks for your work! This PR is a suggestion for replacing current TravisCI with github Actions Current issues: * Current readme is pointing to...
Another try to add multi-schema support #91. This PR uses the solution proposed in PR #160 in a slightly changed form, based on the latest master. Changes mostly concern: -...
I figured out that the server accepts values for `Int` and `String` scalars that don't follow the type defined in the schema. This PR adds simple checks to `Int` and...
Currently it is only possible to serve one GraphQL schema on an Erlang node. It would be useful to be able to run multiple GraphQL schemas on a single node...
**Description:** OTP 24 has introduced the built-in-function `erlang:alias/1`. This has created a name clash in `graphql_execute.erl` as it defines its own function `alias/1` and does not invoke it by the...
This was resulting in `rebar3_hex` and `geas_rebar3` being pulled-in as a dependency needlessly in downstream projects in some situations. More on plugins vs project plugins: https://rebar3.readme.io/docs/using-available-plugins
