|
|
|
|
version: 2
|
|
|
|
|
|
|
|
|
|
defaults: &defaults
|
|
|
|
|
working_directory: ~/ledger-live-desktop
|
|
|
|
|
docker:
|
|
|
|
|
- image: circleci/node:8.11.3-stretch-browsers
|
|
|
|
|
|
|
|
|
|
jobs:
|
|
|
|
|
build:
|
|
|
|
|
<<: *defaults
|
|
|
|
|
steps:
|
|
|
|
|
- run: sudo apt-get update
|
|
|
|
|
- run: sudo apt-get install -y libudev-dev
|
|
|
|
|
- run:
|
|
|
|
|
name: Install latest yarn
|
|
|
|
|
command: |
|
|
|
|
|
curl -sS http://dl.yarnpkg.com/debian/pubkey.gpg | sudo apt-key add - ;
|
|
|
|
|
echo "deb http://dl.yarnpkg.com/debian/ stable main" | sudo tee /etc/apt/sources.list.d/yarn.list ;
|
|
|
|
|
sudo apt-get update && sudo apt-get install yarn
|
|
|
|
|
sudo rm /usr/local/bin/yarn # remove docker yarn
|
|
|
|
|
- checkout
|
|
|
|
|
- restore_cache:
|
|
|
|
|
keys:
|
|
|
|
|
- v12-yarn-packages-{{ checksum "yarn.lock" }}
|
|
|
|
|
- run: yarn install
|
|
|
|
|
- save_cache:
|
|
|
|
|
key: v12-yarn-packages-{{ checksum "yarn.lock" }}
|
|
|
|
|
paths:
|
|
|
|
|
- node_modules
|
|
|
|
|
- run: yarn lint
|
|
|
|
|
- run: ./node_modules/.bin/prettier -l "{src,webpack,.storybook,static/i18n}/**/*.js"
|
|
|
|
|
- run: yarn flow --quiet
|
Rework persistence data layer
Closes #1235
This commit introduce a pretty big change on how app data files are
managed. Instead of having multiple `accounts.json`, `settings.json`,
`user.json`, `countervalues.json`, it now store everything in a single
`app.json`. And it does it in an *async* way, so it should prevent some
frame loss.
Migration will be seamless, and will keep `accounts.json` encryption if set.
So no user action is involved.
This changes comes also with some simplification on password handling
(e.g: no more need to store password hash).
/!\ Disclaimer
During development, I ran about a weird issue (~ 3 or 4 times) when my
data was simply "erased" in the file, so back to onboarding, no more settings,
etc. I suspect race/write condition, something with write-file-atomic, but I
didn't managed to reproduce, everytime I tried. Anyway, I feel not 100% confident
with it, so if you guys can test on your side, with your data (with encryption
key or not) it will help a lot!
7 years ago
|
|
|
- run: yarn test
|
