perf: defer unused nested rich-text schemas and reuse client conversions - #18474
Open
Stevemoretz wants to merge 2 commits into
Open
Stevemoretz wants to merge 2 commits into
Stevemoretz wants to merge 2 commits into
Conversation
Stevemoretz
marked this pull request as ready for review
October 3, 2026 15:33
Stevemoretz
requested review from
AlessioGr,
JarrodMFlesch and
jacobsfletch
as code owners
October 3, 2026 15:33
This branch has not been deployed
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
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.
Nested rich-text editors expand into millions of schema paths. Eager server traversal blocks the event loop; client conversion and feature serialization duplicate shared definitions.
This change reuses conversions by object identity within one context, defers declared native editor schemas until lookup, and gives native blocks/link/upload clients their declared schema roots. Custom features without declared keys retain eager generation and full descendant maps. Ordinary Map callers retain native traversal. Enumeration preserves insertion order; overrides, deletion/reinsertion and clear are covered. No schema paths or stored documents change.
Validation:
Ready for maintainer review. The complete Payload workspace integration/browser matrix has not been run locally and still needs upstream CI validation before merge. Full enumeration still materializes the map, and admin rendering can still occupy the event loop; this does not claim hard real-time isolation for colocated WebSockets.