After studying the notmuch API myself I'm now realising what you meant in purebred-mua/purebred#35 that notmuch has threading built in. Which makes this merge request probably not very useful.
Thinking about it we should make use of that, the NotmuchMail becomes a NotmuchItem and exposes a similar if not the same API for threads and mails (perhaps a different constructor?). A rendering class then can render different views of the item.
After studying the notmuch API myself I'm now realising what you meant in purebred-mua/purebred#35 that notmuch has threading built in. Which makes this merge request probably not very useful.
Thinking about it we should make use of that, the
NotmuchMailbecomes aNotmuchItemand exposes a similar if not the same API for threads and mails (perhaps a different constructor?). A rendering class then can render different views of the item.