Skip to content

Latest commit

 

History

History
41 lines (30 loc) · 2.04 KB

Changelog.md

File metadata and controls

41 lines (30 loc) · 2.04 KB
Raw

Changelog

This document lists changes made in each released version of Lexical.

0.2 (Wed 15th November 2023)

API breaking changes

  • Node type is now provided by a getType() method: #47

Fixes

  • Fixed memory leaks: #40, #44
  • Improvements to typing logic, particularly when replacing characters.
  • Fixed the "insert link" UI within the playground for situations where no text is selected.

Features

  • performRangeSearch() and performRangeSearchWithPayload() functions, to help converting Lexical EditorStates into a format used by backends/APIs which work with string ranges.
  • Undo/redo (aka History) is now in a plugin rather than core
  • SelectableDecoratorNode allows implementing a decorator that handles click-to-select. Improvements to NodeSelection allow pressing backspace to delete selected decorators, etc. SelectableImageNode provides an example use of this. (Still to do, allow theming the selection ring, and allow customising more behaviour!)

0.1 (Wed 5th July 2023)

  • Initial release

  • Features

    • Lexical API re-implemented in Swift
    • LexicalView, a rich text editor for use within UIKit
    • An example Playground app, containing a sample implementation of a rich text toolbar
    • JSON serialization
    • HTML export (work in progress)
    • Decorator node API allows embedding inline UIViews that move with the text
    • Embedded inline images
    • Bulleted and numbered lists
    • Theming support based on NSAttributedString attributes
    • Plugin interface, including commands, listeners, and custom drawing routines
    • A read-only Lexical renderer LexicalReadOnlyView (currently undocumented)
    • Initial read-only support for tables

  • A note on API stability

    • For versions before we hit 1.0, any breaking changes of the API will be accompanied by an increase in the second version digit. For example, a 0.1.1 release will not contain breaking API changes (although it may contain API additions); whereas a 0.2 release may contain breaking changes. We will attempt to mention any such changes in the release notes.