AngularBellApp using couch 2.0. Part of OLE
Clone or download
Type Name Latest commit message Commit time
Failed to load latest commit information.
.travis Use couchdb 2.2.0 (#2101) Sep 17, 2018
design Add activity reports (fixes #1861) (#1863) Oct 4, 2018
docker myPlanet_v0.2.36 (#2975) Jan 15, 2019
e2e ng e2e test for Angular 6 (fixes #1436) (#1506) Jul 3, 2018
git-hooks Vagrant for production (#2409) Nov 1, 2018
src Fix exam submit when changing question (fixes #2984) (#2985) Jan 16, 2019
.dockerignore Prod version of planet docker (connects #4) (#86) Nov 7, 2017
.editorconfig Angular Prototype Aug 23, 2017
.gitattributes Vagrantfile: switch to box 0.2.2 (#103) Oct 24, 2017
.gitignore Ignore planet yml file in main directory (fixes #1730) (#1735) Jul 25, 2018
.htmlhintrc [#260] scss linting (Fixes #260) (#261) Jan 9, 2018
.travis.yml Mobile error log database (fixes #2689) (#2692) Dec 12, 2018 Create (#1065) May 22, 2018
LICENSE Create LICENSE Nov 14, 2017 README: Links to angular and material docs (fixes #1275) (#1495) Jun 28, 2018 Add i18n section to style guide (fixes #1342) (#1565) Jul 18, 2018
Vagrantfile Upgrade to Angular 7 (fixes #2010) (#2511) Nov 20, 2018
angular.json Add Roboto font for Angular Material (#2968) Jan 15, 2019 Fix send survey user filter as non-admin (fixes #2736) (#2840) Dec 27, 2018
crowdin.yml ISO 639-2 (#1360) Jun 18, 2018
karma.conf.js Update to angular 6 (fixes #881) (#1247) Jun 7, 2018
package.json Update version (#2980) Jan 16, 2019
protractor.conf.js add e2e tests (protractor) (fixes #28) (#50) Sep 27, 2017
sass-lint.yml [#260] scss linting (Fixes #260) (#261) Jan 9, 2018
tsconfig.json Add PouchDB base service (#1355) Jun 28, 2018
tslint.json Drop Down List on Profile (fixes #1332) (#1335) Jul 3, 2018

Maintainability Build Status

BeLL apps Angular reboot prototype Planet

Project to create a prototype for a reboot of the BeLL apps using Angular5 & CouchDB2.

Link to Angular Doc and Material Design.

To work on this

The only prerequisite is Vagrant. If you don't know about it, please do some research and try it. After cloning the repository, run vagrant up in the console. Once it's done installing the virtual machine it'll automatically start compiling the app. After about 10 seconds, you can open the app at localhost:3000.

Project guidelines

  • Please check out the project page for available tasks to work on.
  • Before contributing also be sure to read our style guide
  • Please clone the repository rather than forking, unless you're from outside the organization. It's easier for us to collaborate from a new branch on the same repository.
  • After cloning the repository please run npm run install-hooks to add the git hooks to your local repository.
  • If you see something that needs work, please create an issue. If the issue is on the frontend, please try to make it specific to one component.
  • To work on an issue, create a new branch with a descriptive title.
  • Please wait for at least two positive reviews before merging a PR into the master branch

Unit & end-to-end tests

There are two ways for running the tests. The first listed works from the host machine, and the second works after vagrant ssh and cd /vagrant:

npm run v-test (from host) or ng test (from vagrant) - Unit tests Open localhost:9876 once this is done compiling

npm run v-e2e (from host) or ng e2e (from vagrant) - End-to-end tests Results will appear in the console

Additional commands

Similarly, we have a few other npm commands that work from the host machine to run the ng commands from the Angular CLI

npm run v-serve = ng serve

npm run v-build = ng build

npm run v-lint = ng lint

npm run v-lint-fix = ng lint --fix This will fix any lint errors that TSLint can automatically fix

Also, the npm start command can include an additional LNG variable to serve from different language files. This must be run from within the vagrant (so after vagrant ssh and cd /vagrant) and runs in the format:

LNG=es npm start

This would serve the app from the Spanish language files.


I switched branches and now I'm missing a dependency...

The ideal solution would be to ssh into your vagrant and run npm install:

vagrant ssh
cd /vagrant
npm install

This doesn't always work. If you're having trouble or need to revert to the exact dependencies listed on the package.json, you need to remove all packages then install (after cd /vagrant above, run the commands):

rm -rf node_modules/*
npm install

The trailing /* will remove all files & sub-directories of node_modules. You won't be able to remove node_modules because of the link between the vagrant VM and your host.

Cannot GET /

There are two things you can try for this. First involves the node-sass module which can be problematic. You will need to rebuild it from the VM:

vagrant ssh
cd /vagrant
npm rebuild node-sass

The second is to rebuild the application. First you need to cancel the app in the screen with screen -x then CTRL-C. Then you can bring the app back up with one of the above commands or in another screen session with screen -dmS build bash -c 'cd /vagrant; ng serve'.