Skip to content

Requirement: Add TEXT Subtask Navigation To Plan Reading Flow #237

Description

@tentamdin

Description

Update the plan reading/preview flow so plan subtasks with content_type: "TEXT" are treated as navigable reading items alongside existing content_type: "SOURCE_REFERENCE" subtasks.

Current Behavior

Plan navigation currently only supports subtasks where:

"content_type": "SOURCE_REFERENCE",
"source_text_id": "...",
"segment_ids": [...]

These open ReaderScreen using source_text_id.

New Behavior

Plan subtasks can now be either:

"content_type": "SOURCE_REFERENCE"

or:

"content_type": "TEXT",
"content": "some text..."

Validation rules:

  • SOURCE_REFERENCE is valid when source_text_id is non-null and non-empty.
  • TEXT is valid when content.trim() is non-empty.

Illustration
https://link.excalidraw.com/l/9MjBj0OINTj/1GK5oP8VcvL

Metadata

Metadata

Labels

No labels
No labels

Type

No type

Fields

No fields configured for issues without a type.

Projects

Status
DONE

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions