I'm using lacinia and defining a type, there is a way to define an "OR" type

like

{:object {:a {:fields {:b {:type (or nil Int)}}}}

?

:type (non-null Int)

because GraphQL is returning me like:

errors": [
    {
      "message": "Invalid value for a scalar type.",
      "locations": [
        {
          "line": 4,
          "column": 3
        }
      ],
      "path": [
        "b"
      ],
      "extensions": {
        "type": "Int",
        "value": "\"\""
      }

but I want to type "b" be nullable

sometimes b does not have a value

I will mock to a String then... =\

clj -Srepro -Sdeps '{:deps {com.walmartlabs/lacinia {:mvn/version "0.31.0"}}}' -e "(require '[com.walmartlabs.lacinia.schema :as schema]) (schema/compile '{:object {:a {:fields {:b {:type Int}}}}})" works in my machine

clj -Srepro -Sdeps '{:deps {com.walmartlabs/lacinia {:mvn/version "0.31.0"}}}' -e "(require '[com.walmartlabs.lacinia.schema :as schema]) (schema/compile '{:object {:a {:fields {:b {:type (non-null Int)}}}}})" too

types are nullable by default in graphql (I don’t know about Lacinia specifically)

were you trying to return an empty string?

yeah, empty string or number

I used String type

I don't think gql lets you have a type that is either a number or string

it kinda does but it's gross

Or, you'd have to explicitly create a union type and then declare that in your schema

More commonly I think you'd define an object that had both a string and a number field, and leave one or the other as null.

I don't know about gql genrally, but lacinia won't let you have scalars as members of union types. What you could do is create a custom scalar.

What libraries /solutions do you use around GraphQL?

graphql-clj vs lacinia?

Lacinia looks better supported from github stats

oh I see both of this libraries based on different inputs

Is lacincia stable to use on production?

Can I translate schema.edn to schema.txt ? I mean from edn format to standard GraphQL format

yes

how?

many people are using lacinia in production

oh it was answer for first question 🙂

you can also use introspection to generate the GraphQL SDL

Do you use login only in GraphQL or by REST and later allow users to use GraphQL?

we have an authentication/authorization layer that is separate from GraphQL

why?

I am trying to decide about that now 🙂

we have other services that aren't GraphQL

we have a service specifically for authentication, another for authorization

it made more sense for our system