Foundry376/Mailspring
1
1
Fork 0
mirror of https://github.com/Foundry376/Mailspring.git synced 2025-03-02 02:53:01 +08:00
Code Issues Projects Releases Packages Wiki Activity

[models] Remove unnecessary Reply-To array length validation

Browse source 
Summary:
I have quite a few emails in my mailbox that have both multiple Reply-To
addresses. This is perfectly OK by the spec.

Fixes: T7369

Test Plan:
regression test coming - making a list and planning to update all the tests once I've hammered out the current crop of fixes I've identified

I also tested and made sure that N1 does the right thing in this case...
multiple Reply-To addresses are displayed correctly, and when you hit "Reply" a
new draft is started with both in the To: field. Makes sense given this is
something the Python sync engine supported too.

Reviewers: jackie

Reviewed By: jackie

Differential Revision: https://phab.nylas.com/D3558
This commit is contained in:
Christine Spang 2016-12-23 14:30:39 -08:00
parent dda0830220
commit 99899be7c2
1 changed files with 0 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

1
packages/local-sync/src/models/message.js
View file

@ -48,7 +48,6 @@ module.exports = (sequelize, Sequelize) => {
cc: JSONArrayColumn('cc'), cc: JSONArrayColumn('cc'),
bcc: JSONArrayColumn('bcc'), bcc: JSONArrayColumn('bcc'),
replyTo: JSONArrayColumn('replyTo', { replyTo: JSONArrayColumn('replyTo', {
validate: {validateArrayLength1: getLengthValidator('Message.replyTo', 0, 1)},
allowNull: true, allowNull: true,
}), }),
inReplyTo: { type: Sequelize.STRING, allowNull: true}, inReplyTo: { type: Sequelize.STRING, allowNull: true},