Foundry376/Mailspring
1
1
Fork 0
mirror of https://github.com/Foundry376/Mailspring.git synced 2024-11-11 10:12:00 +08:00
Code Issues Projects Releases Packages Wiki Activity
Mailspring/build
History
Evan Morikawa f2517ea7d7 refactor(name): rename worker-sync package to deltas 
Summary:
This diff is a rename. No logical changes.

We used to have a set of files called `nylas-sync-worker`. In Old N1 these
used to have a lot of logic to slowly sync mail from our API. Since we
exclusively use local-sync via a soon-to-be-obsolesced delta stream, these
files really just manage the delta streaming connection.

It's incredibly confusing to have a set of files called worker-sync when
there's a sync-worker already in the codebase. This renames everything to
refer to them as account sync workers.

The reason I wanted this rename is because the IdentityStore on initial
launch triggers and fires a fairly scary-sounding
`Actions.refreshAllSyncWorkers()`. In reality all it does is
`Actions.refreshAllDeltaConnections()`. I'm also tired of staring at files
for a full minute before realizing that this is not the sync worker I was
  looking for.

Test Plan:
After rename, booted the app and ensured that deltas were coming through
for new mail and no errors were being thrown

Reviewers: halla, juan

Reviewed By: juan

Differential Revision: https://phab.nylas.com/D3767
2017-01-25 10:08:23 -05:00
..
config feat(lint): upgrade linter and add exceptions for dumb new rules 2016-11-15 09:56:39 -08:00
resources refactor(name): rename worker-sync package to deltas 2017-01-25 10:08:23 -05:00
tasks fix(build): add output log interval to prevent travis from dying 2017-01-24 14:27:32 -05:00
Gruntfile.js feat(build): build DMG 2017-01-20 12:01:07 -08:00
local-ci.sh feat(build) add npm run local-ci 2017-01-24 14:09:17 -05:00
package.json feat(build): build DMG 2017-01-20 12:01:07 -08:00
README.md Adding node version information to build/README.md 2015-10-05 23:43:33 -07:00

README.md

N1 Build Environment

Node version 0.10.x (Due to the version of electron currently used.)

N1 Building and Tasks

This folder contains tasks to create production builds of N1

Tasks should not be executed from this folder, but rather from /scripts. The /scripts folder has convenient methods that fix paths and do environment checks.

Note that most of the task definitions are stored in /build/tasks

Some useful tasks

NOTE: Run all of these from the N1 root folder.

Linting:

`script/grunt lint`

Building:

`script/grunt build`

The build folder has its own package.json and is isolated so we can use npm to compile against v8's headers instead of apm