Skip to content

Markdown file support #7

@alex-dixon

Description

@alex-dixon

Just imagining what this could look like and what is close to working or possibly working already.

Probably works

  • Import TypeScript files using the normal module resolution algorithm
  • Evaluate code
  • Define vars (expect a namespace for the markdown file)

Benefits

  • Interactive documentation
  • A defined space for REPL scripts, experiments that is clearly outside program/production code.
    • An in-line implementation that would enable this and feature good ergonomics is unclear
    • A separate “special” file extension or ts file can work but advantages over markdown out of the box are not clear. Lacks expressive formatting support etc. Does depend on editor parity with ts code blocks in md relative to ts files

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions