graphql

2022-03-09T08:37:23.376599Z

The dataloader project @hlship refers to is probably https://github.com/oliyh/superlifter which was built precisely to tackle the n+1 problem

2022-03-09T08:40:35.522849Z

It really depends how diverse your graph / root queries / backend sources are. It sounds like @hlship has relatively few root queries (or resolvers, anyway) which can be optimised with their look-ahead approach. If you have a wide range of root queries with many possible edges in your graph you may prefer to have more, smaller resolvers that you can reuse, but they will be less efficient unless you use the dataloader pattern

orestis 2022-03-09T13:19:54.396609Z

I'm trying to update to Lacinia 1.1 and various checks we have complain about io.aviso.pretty not being available: I think there's a PR for this here: https://github.com/walmartlabs/lacinia/pull/403

👍 1
orestis 2022-03-09T13:20:45.315539Z

I wasn't quite sure what to make of this - I've added io.aviso.pretty as a dependency but still see the same error in CI...

orestis 2022-03-09T13:22:10.243279Z

Disregard the above, there are failing tests related to the update, the compilation checks are now passing.