feat(gatsby): Materialization

[freiksenet]

Add a node backend independent materialization layer that triggers when nodes are searched on fields only available through resolvers.

In addition, this fixes various incompatibilities that loki had due to never being tested through materialization.

In addition, node tracking is now happening on node-model level too.

In addition, this adds extensions to decide which fields are sortable and searchable and which needs resolve, so we can materialize.

Can be tested via gatsby@materialization

[stefanprobst]

getQueryFields, mergeObjects, merge, pathToObject, dropQueryOperators are now in node-model and can be removed from db/common/query i think

[freiksenet]

Published as gatsby@2.14.0-rc.3 / gatsby@materialization

[freiksenet]

getQueryFields, mergeObjects, merge, pathToObject, dropQueryOperators are now in node-model and can be removed from db/common/query i think

Cheers, fixed.

[wardpeet]

I still have to go through packages/gatsby/src/schema/node-model.js but I already have some small nits. Nothing big, feel free to ignore

[freiksenet]

Published as gatsby@2.14.0-rc.4 / gatsby@materialization

[wardpeet]

Small nit but I believe this is ready to go! <3

[wardpeet]

Awesome work @freiksenet! lets 🚢 it

[sidharthachatterjee]

Let’s ship this! 💃🏼

[jonsherrard]

Hello all! I am way way out of my depth here - hot reloading is like complete magic to me, but I'm 50% sure this PR broke hot reloading in mdx-deck jxnblk/mdx-deck#474. I've explained a bit more in that issue... I'd like to help more but I think it'll take me literally weeks to understand what Materialization is 😅

If anyone can point me in any directions I'm happy to keep on with my knowledge-less brute-force debugging! 😄 @freiksenet