4.18.1.1686
94%

Ran 03 Oct 2026 08:44PM UTC

Jobs 1

Files 176

Run time 1min

Badge

Embed ▾

Committed 03 Oct 2026 08:39PM UTC coverage: 92.67%. Remained the same

Build # 4.18.1.1686

Build Type

push

coveralls.net

Committed by

jstedfast

Commit Message

Removed the FIXME about making MessageThread.UniqueId non-nullable

After evaluating the change for MailKit 5.0, MessageThread.UniqueId will
remain a UniqueId? rather than using UniqueId.Invalid as a sentinel:

* It would be a silent breaking change for some consumers. Code such as
  `thread.UniqueId != null` or `thread.UniqueId is UniqueId uid` would
  continue to compile (at most with a CS0472 warning) but would always
  evaluate to true, causing dummy parent nodes to be treated as real
  messages with a UID of 0.
* UniqueId? is the established convention for "may be absent" in
  MailKit's public API (MessageEventArgs.UniqueId, IMailFolder.UidNext,
  SearchResults.Min/Max, Append's return value, etc.), so changing only
  MessageThread would not make the API more consistent.
* With nullable reference types enabled, the compiler forces callers to
  handle a missing UID. A sentinel value is easy to forget and would
  only fail at runtime (e.g. when passed to Fetch or Store).
* The benefits (slightly terser code and a few bytes per node) are
  negligible.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

Coverage Stats

24034 of 25935 relevant lines covered (92.67%)

0.93 hits per line

Jobs

ID	Job ID	Ran	Files	Coverage
1	4.18.1.1686.1	03 Oct 2026 08:44PM UTC	176	92.67

jstedfast / MailKit / 4.18.1.1686
94%

README BADGES
x

Markdown

Textile

RDoc

HTML

Rst

Jobs

Source Files on build 4.18.1.1686

jstedfast / MailKit / 4.18.1.1686 94%

README BADGES x

Markdown

Textile

RDoc

HTML

Rst

Jobs

Source Files on build 4.18.1.1686

jstedfast / MailKit / 4.18.1.1686
94%

README BADGES
x