-
Notifications
You must be signed in to change notification settings - Fork 275
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Upgrade guide entry] Upgrade entry for new Pages editing architecture for field components #1815
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good
docs/upgrades/unreleased.md
Outdated
@@ -113,3 +113,5 @@ | |||
* Introduce a new _lib/graphql-editing-service.ts_ file to initialize a _graphQLEditingService_ to support a new Editing Metadata Mode. Can be done by adding this file from the latest version introduced in _nextjs-xmcloud_ base template. | |||
|
|||
* Update _lib/page-props-factory/plugins/preview-mode_ plugin to support a new Editing Metadata Mode. Can be done by replacing this file with the latest version introduced in _nextjs-xmcloud_ base template. | |||
|
|||
* To support editing for fields in Pages, the new editing metadata architecture relies on the new metadata property 'field.metadata' (instead of on 'field.editable', which won't be used in this scenario). If you are using the new editing arhitecture in Pages (EditMode.Metadata) and have custom field component that manipulates or relies on 'field.editable' in some way, it may need to be reworked. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you provide some code sample, please? Customer will still need to support field.editable since it's required for Experience Editor support
docs/upgrades/unreleased.md
Outdated
... | ||
export const Banner = (props: ImageProps): JSX.Element => { | ||
... | ||
const isMetadataMode = sitecoreContext?.editMode === EditMode.Metadata; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
let's show how to access sitecoreContext variable, and add required imports for useSitecoreContext and EditMode variables
Description / Motivation
This PR adds upgrade entry for new Pages editing architecture for field components
Testing Details
Types of changes