Gatsby preview

• same as beta3
• support all 'primitive' elements update handling
  • text
  • number
  • url_slug
  • custom element
  • date & time
• every change is replacing all (supported) elements not just the one lised as edited
  • mainly because url_slug autogeneration -> this field is changed immediately withing the source text element
• ⚠️ currently fails on update if the site is using createNodeField

Gatsby preview

• support all 'primitive' elements update handling
  • text
  • number
  • url_slug
  • custom element
  • date & time
• every change is replacing all (supported) elements not just the one lised as edited
  • mainly because url_slug autogeneration -> this field is changed immediately withing the source text element

Gatsby preview

• support text, number and URL slug element
• fix setting the node type when updating the node
  • was based on item codename - should be item type

4.1.0-beta1 - Gatsby preview 💪

• only for text elements
• Works with the custom element that is watching changes
  • https://github.com/Simply007/gatsby-preview-custom-element

Re-release package an mark it as the latest version

• original release

• Upgrade summary

Upgrade to Kentico Cloud JavaScript SDK v6

#49 - Gatsby package moved to dev dependencies

New Features

• Rich text element now contains structured data
  • images
  • inline linked items
  • links
• Circular references modelled in Linked items element are currently supported and it is possible to querry them

All features are listed in features section.

Breaking changes

• Linked items element data are currently right under the field name (not with suffix _nodes)
• Language variant relation now does contain only items from other languages (doesn not include the same language)

Internal details

• Upgrade to JS SDK v5.4.0
• Refactoring of content item parsing
• split functionality to decorators
• Extended tests for rich text resolution tests
• cycle detection tests
• used new test http service for mocking responses from KC

• Upgrade to JS SDK v5.4.0
• Refactoring of content item parsing
• Extended tests for rich text resolution by linked items + images checks
• Readme polishing
  • New Troubleshoot in Readme
  • Mention that content components are not present at linked items property in RichText element

Breaking change since beta1 (caused by JS SDK upgrade):

• property image_id is renamed to imageId for Assets Element since the image resolution is made my new version of JS SDK.
• property itemId from links from rich text element is renamed to linkId

• Upgrade to JS SDK v5.4.0
• Refactoring of content item parsing
• Extended tests for rich text resolution by linked items + images checks
• Readme polishing
  • New Troubleshoot in Readme
  • Mention that content components are not present at linked items property in RichText element

Breaking change since beta1: property image_id is renamed to imageId for Assets Element since the image resolution is made my new version of JS SDK.

Testing release

Breaking changes

• Linked items element data are currently right under the field name (not with suffix _nodes)
• Language variant relation now does contain only items from other languages (doesn not include the same language)

New Features

• Rich text element now contains structured data
  • images
  • inline linked items
  • links
• Circular references modelled in Linked items element are currently supported and it is possible to querry them

• Implement rich text resolution #44

Rename property name containing resolved HTML