mooncakes.io

cli
→
cmd
→
core
→
dom
→
linkify
→
markdown
→
parser
→
sanitize
→
selector
→
serializer
→
stream
→
tokenizer
→
transform
→
README
U
CliReadPlan
U
CliResult
U
DecideAction
U
DisallowedTagHandling
U
DoctypeInfo
U
FragmentContext
U
HtmlContext
U
HtmlError
U
HtmlToken
U
LinkMatch
U
LinkifyConfig
U
Node
U
NodeKind
U
ParseError
U
ParsedHtml
U
SanitizationPolicy
U
SanitizeTransformObserver
U
SelectorLimits
U
StreamDoctypeEvent
U
StreamEvent
U
StreamSink
U
StreamStartEvent
U
TagKind
U
TagToken
U
TokenizedHtml
U
TransformSpec
U
UnsafeHandling
U
UrlFilter
U
UrlHandling
U
UrlPolicy
U
UrlPolicyRule
U
UrlProxy
U
UrlRule
V
apply_transforms
V
cli_help
V
cli_read_plan
V
comment
V
css_preset_text
V
default_document_sanitization_policy
V
default_sanitization_policy
V
doctype
V
document
V
element
V
find_links
V
find_links_with_config
V
fragment
V
linkify_dom
V
matches
V
parse
V
parse_bytes
V
parse_fragment
V
query
V
query_one
V
run_cli_bytes
V
run_cli_with_reader
V
sanitize_dom
V
stream
V
stream_bytes
V
stream_bytes_each
V
stream_each
V
text
V
to_html
V
to_markdown
V
to_test_format
V
to_text
V
tokenize

README

bobzhang/html_parser/cli does not have a README file

#
CliReadPlan

pub(all) enum CliReadPlan {
  CliImmediate(CliResult)
  CliReadPath(String)
} derive(Eq, @moonbitlang/core/debug.Debug
Debug)

Describes how the CLI should obtain input after argument parsing.

CliImmediate means parsing already produced a complete result, such as help, version output, or an argument error. CliReadPath asks the caller to read the given path, where "-" conventionally means standard input.

#
CliResult

source

pub(all) struct CliResult {
  exit_code : Int
  stdout : String
  stderr : String
  file_output_path : String?
  file_output_content : String?
} derive(Eq, @moonbitlang/core/debug.Debug
Debug)

Result produced by the embeddable CLI runner.

stdout and stderr contain terminal output. When file_output_path is present, file_output_content contains the bytes that a shell wrapper should write to that path instead of printing to standard output.

#
cli_help

source

fn cli_help() -> String

Return the CLI usage text.

#
cli_read_plan

source

fn cli_read_plan(args : ArrayView[String]) -> CliReadPlan

Parse CLI arguments and report whether the caller must read an input path.

Use this when integrating with an environment that performs its own file or standard-input IO. For direct byte input, use run_cli_bytes.

#
run_cli_bytes

source

fn run_cli_bytes(args : ArrayView[String], input : BytesView) -> CliResult

Run the JustHTML-compatible CLI over already-read input bytes.

args should contain only command-line arguments after the executable name. The returned CliResult captures exit status, terminal output, and optional output-file content for the caller to write.

#
run_cli_with_reader

source

fn run_cli_with_reader(args : ArrayView[String], read_input : (String) -> Bytes) -> CliResult

Run the CLI with caller-provided path reading.

The callback receives the input path selected by argument parsing. This is useful for native or embedded hosts that want the library to handle CLI options while the host owns filesystem or standard-input IO.