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

feat: allow for configuring dissolveNamespaces in client #28

Open
ThorstenSuckow opened this issue Feb 13, 2024 · 2 comments
Open

feat: allow for configuring dissolveNamespaces in client #28

ThorstenSuckow opened this issue Feb 13, 2024 · 2 comments
Assignees
Milestone

Comments

@ThorstenSuckow
Copy link
Member

With conjoon 2.0, the general behavior of reading out mailboxes is changed in such a way that "subscriptions" for mailboxes are specified in a filter-string (to keep the backend protocol agnostic and allow for "subscriptions" event if the messaging solution does not support them).

This has an impact on the way the TreeFolderBuilder assembles tree-stuctures - previously those "namespaces" where considered as the root-folders from which the MailFolderList was assembled - now they are considered as namespaces to dissolve.

The value for this option is now hardcoded to ["INBOX", "[GMAIL]"] as default, but should be made available with an option value for a query string that gets passed to the MailFolder-api.

@ThorstenSuckow
Copy link
Member Author

The default values for dissolveNamespaces in Conjoon\MailClient\Data\MailAccount should be removed. Settings must be made available using the imapserver-config or the account data sent by the client.

ThorstenSuckow added a commit to conjoon/rest-api-description that referenced this issue Feb 14, 2024
@ThorstenSuckow
Copy link
Member Author

The default values for dissolveNamespaces in Conjoon\MailClient\Data\MailAccount should be removed. Settings must be made available using the imapserver-config or the account data sent by the client.

done with cb3c0ea

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

No branches or pull requests

1 participant