leviathan
/
pEpForThunderbird
forked from claudio/pEpForThunderbird
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
A clone of ssh://git@git.pep-security.lu:23000/thunderbird/pEpForThunderbird.git, until that one is open source again.
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
1152 Commits
2 Branches
0 Tags
6.3 MiB
 
 
 
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from 'e8af8e6205'
${ noResults }
Go to file
Jorg Knobloch e8af8e6205
Lint all the tests, even the dead ones. 		2 years ago
addon Minor tweaks to modules to get tests going again. 2 years ago
tests Lint all the tests, even the dead ones. 2 years ago
.eslintrc.json Restore "airbnb-base". Oops. See rev. 1f567b1a286a and rev. 224ec02c1e9e. 3 years ago
.hgignore Adjust to new installer directory structure, take 2. 2 years ago
.mocharc.json Move forward Decrypt/Encrypt 4 years ago
DEVELOPMENT.md P4TB-131 add a disclaimer option 3 years ago
Dockerfile Show privacy ratings on emails on decrypt and on composing 4 years ago
Makefile Renamed `chrome` directory to `addon` and related changes. No idea why it was called `chrome` in the first place. 3 years ago
README.md Lint all the tests, even the dead ones. 2 years ago
makeXPI.bat Switch makeXPI.bat from Zip to 7Zip. 2 years ago
manual-and-test.md P4TB-73 use identity `protectionDisabled` for disabled accounts 3 years ago
package-lock.json Change p4t and p4tb to pEp4Tb for chrome:, change preferences to pEp, general cleanup. 3 years ago
package.json Lint all the tests, even the dead ones. 2 years ago

README.md

p≡p for Thunderbird

HOW TO BUILD

Using docker

docker build -t <image_tag> . && docker run -v build:/usr/src/app/build <image_tag>

Using bash

cd addon ; zip -r ../build/pEp4Tb@pEp.security.xpi . ; cd ..

Check syntax statically

You can parse the code with Babel in order to catch syntax errors. After installing with npm install just run:

npm run syntaxCheck

Run ESLint

You can run ESLint to check the style guides defined in .eslintrc.json with the npm script:

npm run lint

ESLint can auto fix some problems with the option --fix but most of them must be fixed manually:

npm run lint --fix
npm run lint -- --fix (on Windows)

Tests

To run tests first is needed to install all dependencies

npm install

Run

npm run test
npm run linttest