Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Email/query Allow listing email #3706

Closed
remk opened this issue Aug 28, 2020 · 3 comments
Closed

Email/query Allow listing email #3706

remk opened this issue Aug 28, 2020 · 3 comments
Assignees
Milestone

Comments

@remk
Copy link
Member

remk commented Aug 28, 2020

Simple implementation without filters/sorting/pagination

Why

With the new specification, I should be able to list my emails:

[[ "Email/query",{
  "accountId": "ue150411c"
}, "0" ]]

Should return :

[[ "Email/query", {
  "accountId": "ue150411c",
  "queryState": "09aa9a075588-780599:0",
  "canCalculateChanges": false,
  "position": 0,
  "ids": [ "Ma783e5cdf5f2deffbc97930a",
    "M9bd17497e2a99cb345fc1d0a", ... ]
}, "0" ]]

HOW

  1. Implement a method for Email/query
  2. Write dedicated integration tests for it.

Notes

Even without sorting the order of the elements should be stable between two calls to the method.
The default sorting order will be the default used by james i.e by ascending order of message uids

DOD

Write memory integration tests for Email/query

@chibenwa
Copy link
Member

Is there a limitation of the Email ids count returned to the client?

How does the client discovers this limitation?

Maybe we can detail which sort / query is implicitly used as well.

@remk
Copy link
Member Author

remk commented Aug 28, 2020

Yes, it will be part of another ticket.
This is only the first basic ticket

@chibenwa chibenwa added this to the Sprint 2 milestone Sep 3, 2020
@remk
Copy link
Member Author

remk commented Sep 9, 2020

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants