The library documents itself · Web & app server
stzMailSandbox
12 own methods · 1 forms written with extensions, listed under their method
the source: base/service/stzMailPort.ring(opens in a new tab) · All classes · The area reference: Web & app server
Under each method, its extensions (Q CS XT Z ZZ IB W U): bold and ticked, it exists; struck, it does not. The extensions and what they mean
No method of this class is run on this page: the class reaches files, the network, processes, the clock, chance or sound, and an example run here would only be an example of its effects. Each method carries the explanation the library gives of itself.
Method
Explanation, as the source carries it
init
(no comment in the source: the name reads as a sentence) initno extension
Send
the PORT contract ----------------------------------------------- capture a message. This is the whole contract a mail port must satisfy; the sandbox records instead of delivering.no extension
IsSandbox
A double says so itself. The registry asks this rather than guessing from a class name, and it is what makes "no sandbox in production" enforceable.no extension
Sent
inspection (what makes the sink assertable)no extension
Count
(no comment in the source: the name reads as a sentence) countno extension
IsEmpty
(no comment in the source: the name reads as a sentence) is emptyno extension
Last
(no comment in the source: the name reads as a sentence) lastno extension
LastBody
(no comment in the source: the name reads as a sentence) last bodyno extension
LastTo
(no comment in the source: the name reads as a sentence) last tono extension
InboxOf
every message addressed to one recipient (their "inbox" in the sink).no extension
Clear
(no comment in the source: the name reads as a sentence) clearQCSXTZZZIBWU
Show
(no comment in the source: the name reads as a sentence) showno extension