Fork me on GitHub
#graphql
<
2021-01-21
>
hlship19:01:50

I'm thinking of doing a lacinia release tomorrow; how many people are using the latest alphas and is anyone hitting any insurmountable problems?

oliy20:01:23

Have used the latest alpha to experiment with Federation gateway, it worked well

orestis19:01:41

We’re shying away from alphas usually, are there breaking changes in this one?

orestis19:01:15

(It seems not but I couldn’t know until I check)

hlship21:01:54

Optional request tracing is now designed to be compatible with Apollo GraphQL's implementation.

New support for Apollo GraphQL Federation.

The default objects names for storing operations are now Query, Mutation, and Subscription, and these must be objects (not unions), as per the GraphQL specification.

Added function com.walmartlabs.lacinia.executor/selection which provides access to the details about the selection, including directives and nested selections.

A new schema compilation option can be used to implement field definition directives by wrapping field resolvers; the selection API can expose information about the field, including a field's type system directives.

Fixed an issue where a Schema Definition Language that contained the literal values true, false, or null would fail to parse.

Lacinia now correctly conforms to the GraphQL specification related to Errors and Non-Nullability.

It is now possible to use query variables inside a list or input object type.

hlship21:01:46

So some behavior changes (watch out for the errors and non-nullability stuff), but the APIs are (I believe) all backwards compatible.

hlship21:01:03

There comes a point where we need to call it 1.0. I haven't really nailed down criteria for that.

hlship21:01:22

We run our alphas in production, at scale.

hlship21:01:02

Hm. We're definitely not hitting the monthly cadence we started with.