Skip to content

Text file editing #5824

Description

@kof

Build first-class text-file workflows around project assets.

Asset text editor

  • Allow uploading supported text files from the Assets panel.
  • Allow creating a new blank text file from the Assets panel.
  • Open supported text assets in an editor dialog on double-click.
  • Edit and persist text content while preserving the stable asset ID.
  • Protect edits from overwriting a newer asset revision.
  • Provide syntax highlighting for every supported editable text format.
  • Show created and last-modified timestamps in asset settings.
  • Support downloading or externally opening asset formats that cannot be edited as text.

Markdown editing

  • Provide common Markdown formatting controls.
  • Provide heading-level selection.
  • Reuse the existing asset picker for Markdown images.
  • Reuse the existing link control for internal and external links.
  • Provide a resizable code/preview split view.
  • Resolve project asset references correctly in Markdown preview.

Asset organization and upload

  • Open assets and folders on double-click while keeping actions available in context and dropdown menus.
  • Support dropping a desktop folder into Assets.
  • Preserve the dropped folder hierarchy instead of flattening its files.
  • Support asset rename, description, folder placement, duplication, replacement, download, and deletion.

Asset API and MCP

  • Expose folder and asset CRUD through MCP.
  • Expose single and batch uploads with folder placement through MCP.
  • Expose revision-safe text-content editing and downloading through MCP.
  • Expose usage lookup, duplication, replacement, and confirmation-gated deletion through MCP.
  • Keep the Builder and MCP content-editing paths on the same reusable storage/revision logic.
  • Support querying assets by extension and filename.
  • Support selecting whether asset contents are included in query results.
  • Define bounded content-query behavior for large or binary assets.
  • Parse JSON asset contents as structured objects when requested.

Data bindings

  • Allow bindable fields to consume selected asset metadata.
  • Allow bindable fields to consume structured data from supported asset contents.

Implementation: Ref #5918

Metadata

Metadata

Assignees

No one assigned

    Labels

    complexity:highMultiple weeks of work or moretype:featFeatures and enhancements

    Type

    No type

    Projects

    Status
    🏗️ In Progress

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions