Allow class instances to be passed onto Gatsby

[JanLenoch]

Summary

Currently, only plain JavaScript objects can be passed onto Gatsby's createNode API method. When a class instance is passed, Gatsby build will fail with an "Unknown field … on type …" GraphQL error (#8053).

Motivation

Our headless CMS has a solid JS SDK that works with class instances by default. We'd like to utilize it to its full potential in Gatsby. We can't ATM.

[pieh]

Some context for this - this check

gatsby/packages/gatsby/src/schema/data-tree-utils.js

Line 174 in eb7648c

} else if (_.isPlainObject(exampleValue)) {

would need to be changed to be smart enough to allow class instances, but blacklist at least some of them (like Date, Number, Array, Map, Set, WeakMap, WeakSet, Promise, ArrayBuffer)

[JanLenoch]

Hi @pieh , just to get an idea: Is this issue somewhere higher in the priority list (if any)? We're currently thinking of doing other plugin development and if the class instance support is on the horizon of say weeks then we'd wait for you to implement it. It would be better than writing code that we'd probably throw away after the class instance support comes. Thanks!

[pieh]

Right now I can't invest any time into doing any development on this, but I'd like to encourage You (or anyone else) to try to implement support for that and open PR (even if it's work-in-progress).

[gatsbot]

Hiya!

This issue has gone quiet. Spooky quiet. 👻

We get a lot of issues, so we currently close issues after 30 days of inactivity. It’s been at least 20 days since the last update here.

If we missed this issue or if you want to keep it open, please reply here. You can also add the label "not stale" to keep this issue open!

Thanks for being a part of the Gatsby community! 💪💜

[arobida]

Hi @pieh , just to get an idea: Is this issue somewhere higher in the priority list (if any)? We're currently thinking of doing other plugin development and if the class instance support is on the horizon of say weeks then we'd wait for you to implement it. It would be better than writing code that we'd probably throw away after the class instance support comes. Thanks!

Out of pure curiosity do you want to use classes for the purpose of using state? @JanLenoch

[JanLenoch]

Hi @arobida , I'm not sure what you mean by saying "for the purpose of using state". Anyways, we'd like to use classes as our HCMS already has a robust JavaScript SDK that provides content as class instances. Simply put, our source plugin does not talk directly to our Delivery/Preview API endpoints. It uses the SDK to do that and consumes the data as class instances.
Did that answer your question?

[gatsbot]

Hey again!

It’s been 30 days since anything happened on this issue, so our friendly neighborhood robot (that’s me!) is going to close it.

Please keep in mind that I’m only a robot, so if I’ve closed this issue in error, I’m HUMAN_EMOTION_SORRY. Please feel free to reopen this issue or create a new one if you need anything else.

Thanks again for being part of the Gatsby community!