This issue focusses on the how and the what. But **why** would we need this? What are the expected benefits of this refactoring? What would it allow application builder to do? Grateful if you can clarify this point @rcordier ...
-- Best regards, Benoit TELLIER General manager of Linagora VIETNAM. Product owner for Twake-Mail product. Chairman of the Apache James project. Mail: [email protected] Tel: (0033) 6 77 26 04 58 (WhatsApp, Signal) Le mars 6, 2026 3:52 AM, de René Cordier (jira) <[email protected]>René Cordier created JAMES-4186: ----------------------------------- Summary: Interface for wrapping email query view in JMAP Key: JAMES-4186 URL: issues.apache.org/jira/browse/JAMES-4186 Project: James Server Issue Type: Improvement Reporter: René Cordier Propose an interface for wrapping email query view in JMAP. Have a Predicate: EmailQueryOptimizer wich basically does EmailQueryRequest => Option[SFlux[MessageId]] Provide a James implementation that bundles EmailQueryView by reusing the predicate => EmailQueryViewOptimizer EmailQueryMethod would traverse a Set. DoD: EmailQueryView tests are still passing. -- This message was sent by Atlassian Jira (v8.20.10#820010) --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
