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

Rework routing, data structures and naming ambiguities #3439

Merged
merged 1 commit into from
Aug 25, 2020

Conversation

ChristophWurst
Copy link
Member

@ChristophWurst ChristophWurst commented Aug 11, 2020

This changes a lot of things

  • Mailboxes are identified by their database ID (as opposed to account ID and name)
  • Messages are identified by their database ID (as opposed to account ID, mailbox name and message UID)
  • Routes are simplified and use the browser history API (as opposed to client-only anchor routes)
  • The Vuex store got a lot simpler, because the normalization is obsolete due to the naturally unique IDs
  • Naming inconsistency of maibox/folder finally resolved -> we call it "mailbox" in the code (as that is the proper name by the standards) and "folder" for the user (because @jancborchardt prefers that)

Required for deep links in #3433 and possibly for threading.

  • (accountId, folderId) to mailbox ID
  • Drafts handling (with db IDs)
  • Sync handling (with db IDs)

Signed-off-by: Christoph Wurst <christoph@winzerhof-wurst.at>
@ChristophWurst ChristophWurst marked this pull request as ready for review August 25, 2020 08:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants