Skip to content

Feature: Add Maximum Change Limit and Optimization for Lexical History Plugin #6728

Description

@dineug

Description

After reading this article, I traced where memory usage increases and found that it differs depending on whether the Lexical history plugin is enabled in the production build environment.

It would be helpful if the Lexical history plugin had an option to set a maximum limit on change history. Additionally, optimizing how changes are stored could improve performance.

Use HistoryPlugin

Lexical-JSHeapUsedSize

None HistoryPlugin

Lexical-JSHeapUsedSize

Impact

This feature would enhance the user experience when editing large documents by providing smoother performance.

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementImprovement over existing feature

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions