release v0.0.22

CHANGELOG.md

@@ -1,21 +1,26 @@
 ## 0.0.22
-- Added support for ENABLE extension, https://tools.ietf.org/html/rfc5161.
+- Breaking API change: use FETCH IMAP methods now return `FetchImapResult` instead of `List<MimeMessage>`
+- Breaking API change: `ImapFetchEvent` now contains a full `MimeMessage` instead of just the sequence ID and flags
+- Added `ImapVanishedEvent` that is called instead of `ImapExpungeEvent` when QRESYNC has been enabled
+- Added support for [QRESYNC extension](https://tools.ietf.org/html/rfc7162)
+- Added support for [ENABLE extension](https://tools.ietf.org/html/rfc5161)
+- Fix handling STATUS responses (issue #56)
 
 ## 0.0.21
-- Added support for ISO 8859-15 / latin9 encoding - based on UTF-8.
+- Added support for ISO 8859-15 / latin9 encoding - based on UTF-8
 
 ## 0.0.20
-- Breaking change: use MessageSequence for defining message ID or UID ranges instead of integer-based IDs
+- Breaking change: use `MessageSequence` for defining message ID or UID ranges instead of integer-based IDs
 
 ## 0.0.19
 - Fix for fetching recent messages when the chunksize is larger than the existing messages - thanks to studiozocaro!
 
 ## 0.0.18
-- Breaking API changes: MimeMessage.body API, get and set text/plain and text/html parts in MimeMessage
+- Breaking API changes: `MimeMessage.body` API, get and set text/plain and text/html parts in MimeMessage
 - Support nested BODY and BODYSTRUCTURE responeses when fetching message data
-- Support CONDSTORE IMAP extension
-- Support MOVE IMAP extension
-- Support UIDPLUS IMAP extension
+- Support [CONDSTORE IMAP extension](https://tools.ietf.org/html/rfc5161)
+- Support [MOVE IMAP extension](https://tools.ietf.org/html/rfc6851)
+- Support [UIDPLUS IMAP extension](https://tools.ietf.org/html/rfc6851)
 
 ## 0.0.17
 - Supports parsing BODYSTRUCTURE responses when fetching message data
@@ -29,27 +34,27 @@
 
 ## 0.0.14
 
-- Save messages to the server with ImapClient.appendMessage().
-- Store message flags using the ImapClient.store() method or use one of the mark-methods like markFlagged() or markSeen().
-- Copy message(s) using ImapClient.copy().
-- Copy, fetch, store or search message with UIDs using ImapClient.uidCopy(), uidStore(), etc.
-- Remove messages marked with the \Deleted flag using ImapClient.expunge()
-- Authenticate via OAUTH 2.0 using ImapClient.authenticateWithOAuth2() (AUTH=XOAUTH2) or authenticateWithOAuthBearer() (AUTH=OAUTHBEARER).
-- You can now switch to TLS using ImapClient.startTls().
-- Query the capabilities using the ImapClient.capability() call.
-- Let the server do some housekeeping using the ImapClient.check() method.
+- Save messages to the server with `ImapClient.appendMessage()`.
+- Store message flags using the `ImapClient.store()` method or use one of the mark-methods like `markFlagged()` or `markSeen()`.
+- Copy message(s) using `ImapClient.copy()`.
+- Copy, fetch, store or search message with UIDs using `ImapClient.uidCopy()`, `uidStore()`, etc.
+- Remove messages marked with the \Deleted flag using `ImapClient.expunge()`
+- Authenticate via OAUTH 2.0 using `ImapClient.authenticateWithOAuth2()` (AUTH=XOAUTH2) or `authenticateWithOAuthBearer()` (AUTH=OAUTHBEARER).
+- You can now switch to TLS using `ImapClient.startTls()`.
+- Query the capabilities using the `ImapClient.capability()` call.
+- Let the server do some housekeeping using the `ImapClient.check()` method.
 
 ## 0.0.13
 
-- Forward complex messages with MessageBuilder.prepareForwardMessage(), too  (issue #24)
+- Forward complex messages with `MessageBuilder.prepareForwardMessage()`, too  (issue #24)
 
 ## 0.0.12
 
-- Forward messages with MessageBuilder.prepareForwardMessage() 
+- Forward messages with `MessageBuilder.prepareForwardMessage()` 
 
 ## 0.0.11
 
-- Adding simple reply generation with MessageBuilder.prepareReplyToMessage() (issue #25)
+- Adding simple reply generation with `MessageBuilder.prepareReplyToMessage()` (issue #25)
 - Improvement for adding larger files (issue #28)
 
 
@@ -87,11 +92,11 @@
 
 ## 0.0.3
 
-- Always end lines with \r\n when communicating either with SMTP or IMAP server, parse iso-8859-1 encoded headers
+- Always end lines with `\r\n` when communicating either with SMTP or IMAP server, parse iso-8859-1 encoded headers
 
 ## 0.0.2
 
-- Cleaning architecture, adding support for BODY[HEADER.FIELDS] messages
+- Cleaning architecture, adding support for `BODY[HEADER.FIELDS]` messages
 
 ## 0.0.1
 

README.md

@@ -86,7 +86,7 @@ Add this dependency your pubspec.yaml file:
 
 ```
 dependencies:
-  enough_mail: ^0.0.21
+  enough_mail: ^0.0.22
 ```
 The latest version or `enough_mail` is [![enough_mail version](https://img.shields.io/pub/v/enough_mail.svg)](https://pub.dartlang.org/packages/enough_mail).
 

lib/imap/events.dart

@@ -21,7 +21,10 @@ class ImapExpungeEvent extends ImapEvent {
 /// Notifies about a sequence of messages that have been deleted.
 /// This event can only be triggered if the server is QRESYNC compliant and after the client has enabled QRESYNC.
 class ImapVanishedEvent extends ImapEvent {
+  /// Sequence of messages that have been expunged
   final MessageSequence vanishedMessages;
+
+  /// true when the vanished messages do not lead to updated sequence IDs
   final bool isEarlier;
   ImapVanishedEvent(this.vanishedMessages, this.isEarlier)
       : super(ImapEventType.vanished);

pubspec.yaml

@@ -1,6 +1,6 @@
 name: enough_mail
 description: IMAP and SMTP clients in pure Dart. Strives to be compliant with IMAP4 rev1, IMAP IDLE, IMAP METADATA Extension and SMTP.
-version: 0.0.21
+version: 0.0.22
 homepage: https://github.com/Enough-Software/enough_mail
 
 environment: