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

Migrate jmap-draft-client to use Mailbox/get & Mailbox/set of jmap-client-ts #388

Open
fabienmoyon opened this issue Mar 17, 2021 · 1 comment
Labels
enhancement New feature or request Major

Comments

@fabienmoyon
Copy link
Member

Currently

We use jmap-draft-client to get and set Mailboxes.

Expected

Migrate to use Mailbox/get & Mailbox/set of jmap-client-ts without altering the current behaviour

JMAP-CLIENT-TS EPIC

https://app.zenhub.com/workspaces/ft---inbox-5f9bf5a7d512f60015b11562/issues/openpaas-suite/jmap-client-ts/31

Link to

linagora/jmap-client-ts#32
linagora/jmap-client-ts#33
linagora/jmap-client-ts#35

@fabienmoyon fabienmoyon added enhancement New feature or request Major labels Mar 17, 2021
@fabienmoyon fabienmoyon added this to the FT Inbox Sprint 8 milestone Mar 17, 2021
@chibenwa
Copy link
Member

  1. Would it be possible to uncorrelated Mailbox/set?

Rationals: Mailbox/get is a pre-requisite for the PUSH, Mailbox/set likely is not...

  1. What are the impacted Angular component?

Would it make sense to have an inventory?

-> This enables evaluating the task
-> This enables cutting the task in subtask as required

  1. Would it be possible to take this opportunity to rewritte some of these components using VueJS and (say) ES6 modules ( https://www.holistics.io/blog/why-and-how-we-migrated-from-angularjs-to-vuejs/ ) ?

(I may be optimistic here but it is worth asking)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request Major
Projects
None yet
Development

No branches or pull requests

2 participants