2016-06-23 05:41:32 +08:00
|
|
|
{
|
2016-11-24 01:00:47 +08:00
|
|
|
"name": "isomorphic-core",
|
2016-06-23 05:41:32 +08:00
|
|
|
"version": "0.0.1",
|
2017-02-17 06:53:20 +08:00
|
|
|
"description": "Packages use isomorphically on n1-cloud and client-sync",
|
2016-06-23 05:41:32 +08:00
|
|
|
"main": "index.js",
|
2017-03-01 07:49:30 +08:00
|
|
|
"scripts": {
|
|
|
|
|
"test": "babel-node spec/run.es6"
|
|
|
|
|
},
|
2016-06-23 05:41:32 +08:00
|
|
|
"dependencies": {
|
2017-02-17 07:36:04 +08:00
|
|
|
"atob": "2.0.3",
|
Revert "Revert "[feat] Add support for send later""
Arc land messed up and landed a not fully merged branch. (Seriously – I
had merged a copy of my branch with master to see how easy it would be.
Because I didn't want to merge the whole thing, I blindly committed my
changes and switched back to my real branch). To my great surprise, arc
decided to use the wrong branch when landing it.
Original commit message:
Summary:
Finally, here it is! Send later, with support for open tracking but
without support for attachments yet. It took me some time to find the
right way to do things.
**The send later dilemna**
There's two ways we could handle send later:
1. do everything on the client
2. process the message in the cloud
1. is very tempting because it would make the cloud server very
simple. Unfortunately, it has some serious limitations, for example,
setting the "Date" message header. That's why I chose to go with 2. When
a user presses the "Send Later" button, we save the open/link tracking
metadata and fills in all the required fields. I added a custom endpoint
to the K2 API to do this, `/drafts/build`. After that, we save the JSON
contents of the message as metadata.
When we process metadata, we simply create a MIME message from the
JSON and send it.
**Limitations**
Right now, send later doesn't support and attachments. There's also
some minor code duplication which needs to be refactored away.
Test Plan: Tested manually. Checked that regular send still worked, too.
Reviewers: mark, spang, halla, juan, evan
Reviewed By: evan
Differential Revision: https://phab.nylas.com/D4054
2017-03-08 08:27:08 +08:00
|
|
|
"btoa": "1.1.2",
|
2017-02-17 04:32:07 +08:00
|
|
|
"imap": "github:jstejada/node-imap#fix-parse-body-list",
|
|
|
|
|
"imap-provider-settings": "github:nylas/imap-provider-settings",
|
2017-03-07 03:35:50 +08:00
|
|
|
"jasmine": "2.x.x",
|
2016-12-06 09:59:47 +08:00
|
|
|
"joi": "8.4.2",
|
2017-02-18 04:41:27 +08:00
|
|
|
"libhoney": "1.0.0-beta.2",
|
2016-12-16 04:04:43 +08:00
|
|
|
"nodemailer": "2.5.0",
|
2016-11-23 08:54:20 +08:00
|
|
|
"promise-props": "1.0.0",
|
|
|
|
|
"promise.prototype.finally": "1.0.1",
|
2017-02-18 04:11:14 +08:00
|
|
|
"rx-lite": "4.0.8",
|
2017-01-05 07:33:12 +08:00
|
|
|
"sequelize": "3.28.0",
|
2016-11-23 08:54:20 +08:00
|
|
|
"underscore": "1.8.3",
|
Revert "Revert "[feat] Add support for send later""
Arc land messed up and landed a not fully merged branch. (Seriously – I
had merged a copy of my branch with master to see how easy it would be.
Because I didn't want to merge the whole thing, I blindly committed my
changes and switched back to my real branch). To my great surprise, arc
decided to use the wrong branch when landing it.
Original commit message:
Summary:
Finally, here it is! Send later, with support for open tracking but
without support for attachments yet. It took me some time to find the
right way to do things.
**The send later dilemna**
There's two ways we could handle send later:
1. do everything on the client
2. process the message in the cloud
1. is very tempting because it would make the cloud server very
simple. Unfortunately, it has some serious limitations, for example,
setting the "Date" message header. That's why I chose to go with 2. When
a user presses the "Send Later" button, we save the open/link tracking
metadata and fills in all the required fields. I added a custom endpoint
to the K2 API to do this, `/drafts/build`. After that, we save the JSON
contents of the message as metadata.
When we process metadata, we simply create a MIME message from the
JSON and send it.
**Limitations**
Right now, send later doesn't support and attachments. There's also
some minor code duplication which needs to be refactored away.
Test Plan: Tested manually. Checked that regular send still worked, too.
Reviewers: mark, spang, halla, juan, evan
Reviewed By: evan
Differential Revision: https://phab.nylas.com/D4054
2017-03-08 08:27:08 +08:00
|
|
|
"xoauth2": "1.2.0",
|
|
|
|
|
"he": "1.1.0",
|
|
|
|
|
"iconv": "2.2.1",
|
|
|
|
|
"mimelib": "0.2.19"
|
2016-06-23 05:41:32 +08:00
|
|
|
},
|
|
|
|
|
"author": "Nylas",
|
|
|
|
|
"license": "ISC"
|
|
|
|
|
}
|
