diff options
Diffstat (limited to 'target/doc/mailparse/index.html')
| -rw-r--r-- | target/doc/mailparse/index.html | 24 |
1 files changed, 13 insertions, 11 deletions
diff --git a/target/doc/mailparse/index.html b/target/doc/mailparse/index.html index 511aa28..0dacece 100644 --- a/target/doc/mailparse/index.html +++ b/target/doc/mailparse/index.html @@ -47,13 +47,13 @@ <a id="toggle-all-docs" href="javascript:void(0)" title="collapse all docs"> [<span class='inner'>−</span>] </a> - </span><a id='src-0' class='srclink' href='../src/mailparse/src/lib.rs.html#1-984' title='goto source code'>[src]</a></span></h1> + </span><a id='src-0' class='srclink' href='../src/mailparse/src/lib.rs.html#1-1024' title='goto source code'>[src]</a></span></h1> <h2 id='structs' class='section-header'><a href="#structs">Structs</a></h2> <table> <tr class=' module-item'> <td><a class='struct' href='struct.MailHeader.html' title='mailparse::MailHeader'>MailHeader</a></td> - <td class='docblock short'> + <td class='docblock-short'> <p>A struct that represents a single header in the message. It holds slices into the raw byte array passed to parse_mail, and so the lifetime of this struct must be contained within the lifetime of the raw @@ -64,7 +64,7 @@ the data as Rust strings.</p> <tr class=' module-item'> <td><a class='struct' href='struct.ParsedContentType.html' title='mailparse::ParsedContentType'>ParsedContentType</a></td> - <td class='docblock short'> + <td class='docblock-short'> <p>A struct to hold a more structured representation of the Content-Type header. This is provided mostly as a convenience since this metadata is usually needed to interpret the message body properly.</p> @@ -73,7 +73,7 @@ needed to interpret the message body properly.</p> <tr class=' module-item'> <td><a class='struct' href='struct.ParsedMail.html' title='mailparse::ParsedMail'>ParsedMail</a></td> - <td class='docblock short'> + <td class='docblock-short'> <p>Struct that holds the structured representation of the message. Note that since MIME allows for nested multipart messages, a tree-like structure is necessary to represent it properly. This struct accomplishes that by holding @@ -84,7 +84,7 @@ a vector of other ParsedMail structures for the subparts.</p> <tr class=' module-item'> <td><a class='enum' href='enum.MailParseError.html' title='mailparse::MailParseError'>MailParseError</a></td> - <td class='docblock short'> + <td class='docblock-short'> <p>An error type that represents the different kinds of errors that may be encountered during message parsing.</p> </td> @@ -93,7 +93,7 @@ encountered during message parsing.</p> <tr class=' module-item'> <td><a class='trait' href='trait.MailHeaderMap.html' title='mailparse::MailHeaderMap'>MailHeaderMap</a></td> - <td class='docblock short'> + <td class='docblock-short'> <p>A trait that is implemented by the Vec<MailHeader> returned by the parse_headers function. It provides a map-like interface to look up header values by their name.</p> @@ -103,7 +103,7 @@ name.</p> <tr class=' module-item'> <td><a class='fn' href='fn.dateparse.html' title='mailparse::dateparse'>dateparse</a></td> - <td class='docblock short'> + <td class='docblock-short'> <p>Convert a date field from an email header into a UNIX epoch timestamp. This function handles the most common formatting of date fields found in email headers. It may fail to parse some of the more creative formattings.</p> @@ -112,7 +112,7 @@ email headers. It may fail to parse some of the more creative formattings.</p> <tr class=' module-item'> <td><a class='fn' href='fn.parse_content_type.html' title='mailparse::parse_content_type'>parse_content_type</a></td> - <td class='docblock short'> + <td class='docblock-short'> <p>Helper method to parse a header value as a Content-Type header. The charset defaults to "us-ascii" if no charset parameter is provided in the header value.</p> @@ -121,7 +121,7 @@ value.</p> <tr class=' module-item'> <td><a class='fn' href='fn.parse_header.html' title='mailparse::parse_header'>parse_header</a></td> - <td class='docblock short'> + <td class='docblock-short'> <p>Parse a single header from the raw data given. This function takes raw byte data, and starts parsing it, expecting there to be a MIME header key-value pair right at the beginning. It parses that @@ -135,7 +135,7 @@ as a MIME key-value pair.</p> <tr class=' module-item'> <td><a class='fn' href='fn.parse_headers.html' title='mailparse::parse_headers'>parse_headers</a></td> - <td class='docblock short'> + <td class='docblock-short'> <p>Parses all the headers from the raw data given. This function takes raw byte data, and starts parsing it, expecting there to be zero or more MIME header key-value pair right at the beginning, @@ -152,7 +152,7 @@ Error values are returned if there was some sort of parsing error.</p> <tr class=' module-item'> <td><a class='fn' href='fn.parse_mail.html' title='mailparse::parse_mail'>parse_mail</a></td> - <td class='docblock short'> + <td class='docblock-short'> <p>The main mail-parsing entry point. This function takes the raw data making up the message body and returns a structured version of it, which allows easily accessing the header and body @@ -181,6 +181,8 @@ information as needed.</p> <dd>Move down in search results</dd> <dt>⏎</dt> <dd>Go to active search result</dd> + <dt>+</dt> + <dd>Collapse/expand all sections</dd> </dl> </div> |