[
https://issues.apache.org/jira/browse/JAMES-3562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17321035#comment-17321035
]
Benoit Tellier commented on JAMES-3562:
---------------------------------------
I am unsure of the best mitigation here...
Implement Thread/changes now would make it harder to change the current Thread
behaviour without some significant work needed.
Could we live with the current implementation until JMAP Threads are decently
implemented?
> Threads/changes created does not contain fake thread
> ----------------------------------------------------
>
> Key: JAMES-3562
> URL: https://issues.apache.org/jira/browse/JAMES-3562
> Project: James Server
> Issue Type: Bug
> Components: JMAP
> Affects Versions: master
> Reporter: Daniel Gultsch
> Assignee: Antoine Duprat
> Priority: Major
>
> I’m doing Email/changes and Thread/changes in the same request.
> The response to Email/changes returns and a newly arrived email id in the
> created list.
> The response to Thread/changes however is empty. With the James’ current
> model of one email one thread I would expect the Thread/changes response to
> inform we of a new thread (that coincidentally has the same ID as the email)
>
> I noticed that Thread/changes did provide me with a new state though. It's
> just that the change itself was completely empty.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
