Repository navigation
v0.1.7
Added
- core — take twig 3.3.1, and write the highlight and the strikethrough Markdown already read (
893a297) - swift — colour a highlight from the toolbar, and everything under it that had to exist first (
e685372) - tui — the highlight's colours, under Format and in the palette — and the compound moves into core (
de95804) - web — a highlight's colour, from the editor's API to the demo's picker (
f6fe368)
Behavioural changes
-
leaf_core::Capabilitiesfor a Markdown document reports
mark: trueandstrike: true, wheremarkwas false.Doc::supportsand
Doc::togglefollow:InlineKind::Markwrites==x==and
InlineKind::Deletewrites~~x~~instead of setting a "not supported in
markdown" status. A toolbar driven by the record — the TUI menu and palette,
the webdata-capattributes, the SwiftCapabilitiesstruct — un-dims
those two buttons with no change of its own. -
Doc::supportsandCapabilities::ofnow answer for a
document parsed with leaf'sparse_extensions, not for twig's default
options. Only the two flags above differ today, but a caller reading these as
a fact about the bare format is reading them wrong: they are a fact about the
document leaf actually builds. -
leaf_core::Capabilitiesgainsmark_color, and
leaf_ffi::Capabilities/ leaf-wasm'sCapabilitiesViewgain the same field.
Rust code constructing aCapabilitiesliteral must add it; the two bindings
hand out records, so a frontend only sees a new field. -
DocViewgainsmark_colorin both bindings — a
MarkColor?in Swift, a colour name ornullin JS. A Swift host building a
DocViewor aLeafUI.EditorStateby hand gets a defaulted parameter and
compiles unchanged. -
LeafEditorModel.highlight(_:)(Swift) is now one undo step
rather than two when it both highlights and colours a selection. A host that
calledundo()twice to reverse one press will now undo the edit before it. -
leaf_core::Docgainshighlight, and both bindings gain a
highlightmethod besideset_mark_color. Nothing existing changes shape. -
EditorState(leaf-web) gainsmarkColorand
hasSelection. A host destructuring the state is unaffected; one comparing
whole state objects will see them differ where they used to match.
Every change in this release and the ones before it: docs/CHANGELOG.md.