You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The JS SDK allows the developer to define so called link resolvers and rich text resolvers. These are methods that operate on Kentico Cloud Rich text elements and produce HTML with hyperlinks and embedded content items.
The source plugin currently builds the _nodes sibling GraphQL properties that contain GraphQL links to content items in a given Rich text element. It also lacks the support for creating (or enriching) the _nodes sibling property based on links. It doesn't do any transformation of the rich text element HTML data.
what it takes to create a transformer plugin that transforms links and content items in Rich text
if the resolvers could be written by developers using the same notation as the JS SDK uses
Also, Gatsby have recently updated their best practice and recommend doing any "enhancement" of source nodes via a transformer plugin (not through a source plugin).
Therefore, consider moving the code that creates the _nodes sibling properties into the new transformer plugin.
Expected result
The JS SDK allows the developer to define so called link resolvers and rich text resolvers. These are methods that operate on Kentico Cloud Rich text elements and produce HTML with hyperlinks and embedded content items.
The source plugin currently builds the
_nodes
sibling GraphQL properties that contain GraphQL links to content items in a given Rich text element. It also lacks the support for creating (or enriching) the_nodes
sibling property based on links. It doesn't do any transformation of the rich text element HTML data.Such a transformation should be dealt with separately using a Gatsby transformer plugin.
Find out:
Also, Gatsby have recently updated their best practice and recommend doing any "enhancement" of source nodes via a transformer plugin (not through a source plugin).
Therefore, consider moving the code that creates the
_nodes
sibling properties into the new transformer plugin.Resources
The text was updated successfully, but these errors were encountered: