moonbitstack/moonmail/examples/browser

README
- ::equalRefused::equal
- ::not_equalRefused::not_equal
- ::to_reprRefused::to_repr
- ::encodeAddress::encode
- ::equalAddress::equal
- ::mailboxesAddress::mailboxes
- ::not_equalAddress::not_equal
- ::to_reprAddress::to_repr
- ::equalAttachment::equal
- ::newAttachment::new
- ::not_equalAttachment::not_equal
- ::to_reprAttachment::to_repr
- ::equalBody::equal
- ::not_equalBody::not_equal
- ::to_reprBody::to_repr
- ::addHeaders::add
- ::allHeaders::all
- ::equalHeaders::equal
- ::getHeaders::get
- ::iterHeaders::iter
- ::lengthHeaders::length
- ::newHeaders::new
- ::not_equalHeaders::not_equal
- ::removeHeaders::remove
- ::setHeaders::set
- ::to_reprHeaders::to_repr
- ::encodeMailbox::encode
- ::equalMailbox::equal
- ::newMailbox::new
- ::not_equalMailbox::not_equal
- ::to_reprMailbox::to_repr
- ::addressesMessage::addresses
- ::attachmentsMessage::attachments
- ::bccMessage::bcc
- ::ccMessage::cc
- ::content_typeMessage::content_type
- ::dateMessage::date
- ::encodeMessage::encode
- ::equalMessage::equal
- ::fromMessage::from
- ::htmlMessage::html
- ::message_idMessage::message_id
- ::newMessage::new
- ::not_equalMessage::not_equal
- ::parseMessage::parse
- ::reply_toMessage::reply_to
- ::subjectMessage::subject
- ::textMessage::text
- ::toMessage::to
- ::to_reprMessage::to_repr
V
encode_addresses
V
format_date
V
parse_address
V
parse_addresses
V
parse_date

moonbitstack/moonmail/examples/browser does not have a README file

engine_call

fn engine_call(op : String, args : String) -> String

The one function the page imports. op names the operation and args is a JSON object; the answer is a JSON object with ok and either value or error. Strings are the only thing that crosses the boundary, which keeps the binding to one function however many methods grow behind it.