Repository navigation
Merge latest into release 23 - #2220
Merged
Merged
Conversation
…sMiddleware (#2201) * fix: Skip malformed redirect regex rules in RedirectsMiddleware * chore: Update CHANGELOG * fix lint issue * Update CHANGELOG.md
…t mode for nested personalization (#2202) * [sitecore-jss] Fix personalize hide component not working properly in edit mode for nested personalization * Updated PR reference
* chore: Update rollup dependency and add minimatch package version 3.1.5 * chore: Change minimatch package reference to nx/minimatch in package.json * chore: Update CHANGELOG to include minimatch dependency resolution for nx --------- Co-authored-by: Shakya Wijerathne <shakya.wijerathne+sitecore@sitecore.com>
…t of 404 errors in Pages (#2206) * Pass NavigationTitle metadata to navigation link fields * changelog updated * Refactor getLinkField to use a more specific NavigationLinkField type * extend linkField with FieldMetadata * Import FieldMetadata directly from sitecore-jss/layout * get fieldmetadata through nextjs-field * Update getLinkField to use FieldMetadata and import FieldMetadata in index
…endered components (#2207) * Stop passing Placeholder internal props to rendered components * Restore ErrorBoundary child prop spreading for withPlaceholder HOC * prettier update * prettier update - placeholdercommon * updated the changelog
…eing incompatible with ESLint 9 (#2208) * Fix Vue template build failure caused by `@vue/cli-plugin-eslint` being incompatible with ESLint 9 * Updated CHANGELOG
* [Sitecore AI] Remove Sitecore Personalize and client-side * Updated yarn.lock * Addressed comments
* Remove Design Studio support * Updated Changelog * Re-generated API docs
* Remove Pages & Metadata mode support * Removed content-styles and updated changelog * Removed EDITING_ALLOWED_ORIGINS list and updated api docs
* Remove Sitecore AI based templates and Edge Proxy support * Removed SITECORE env var references * Re-generated API docs
…rence across re-renders (#2204) * [sitecore-jss-react] Stabilize RichText dangerouslySetInnerHTML reference across re-renders RichText built a new dangerouslySetInnerHTML object on every render. React DOM compares this prop by reference, so every parent re-render re-set innerHTML, recreating all child DOM nodes and dropping the internal-link click/prefetch listeners attached by NextRichText. Memoize the object keyed on the resolved html string so the reference stays stable when content is unchanged. Also dedupe react/react-dom in sitecore-jss-nextjs test setup: with yarn nmHoistingLimits: workspaces, the workspace-linked react package resolves its own React copy, breaking hooks in its components under this package's react-dom. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> * Refactor dangerouslySetInnerHTML handling in RichText * Remove unnecessary blank line in RichText component * CHANGELOG updated Add note about RichText component causing DOM issues on render. --------- Co-authored-by: Claude Fable 5 <noreply@anthropic.com> Co-authored-by: Naveen Hedalla Arachchi <nvhd@sitecore.net>
…gDataCache (@upstash/redis) (#2216) * [nextjs] Replace VercelEditingDataCache (@vercel/kv) with RedisEditingDataCache (@upstash/redis) * Use 'del' command instead of 'expire' * Updated changelog
…L didn't match the client (#2218) * Suppress Experience Editor hydration mismatches in SDK chrome * changelog updated * Suppress hydration warnings for EE components
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description / Motivation
Testing Details
Types of changes