Make sure you have at least the following versions of node
and npm
.
- Node version v5.6.0 or higher
- npm version 3.8.0 or higher
Use the following commands to check your current versions
node -v
npm -v
Clone the repository from github with the following command
git clone https://github.com/dhis2/interpretation-app
Install the node dependencies
npm install
To set up your DHIS2 instance to work with the development service you will need to add the development servers address to the CORS whitelist. You can do this within the DHIS2 Settings app under the access tab. On the access tab add http://localhost:8081
to the CORS Whitelist.
The starter app will look for a DHIS 2 development instance configuration in
$DHIS2_HOME/config
. So for example if yourDHIS2_HOME
environment variable is set to~/.dhis2
, the starter app will look for~/.dhis2/config.js
and then~/.dhis2/config.json
and load the first one it can find.The config should export an object with the properties
baseUrl
andauthorization
, where authorization is the base64 encoding of your username and password. You can obtain this value by opening the console in your browser and typingbtoa('user:pass')
.If no config is found, the default
baseUrl
ishttp://localhost:8080/dhis
and the default username and password isadmin
anddistrict
, respectively.See
webpack.config.js
for details.
This should enable you to run the following node commands:
To run the development server
npm start
To run the tests one time
npm test
To run the tests continuously on file changes (for your BDD workflow)
npm run test-watch
To generate a coverage report for the tests
npm run coverage
To check the code style for both the JS and SCSS files run
npm run lint
React is the view part of the front-end applications, it has a component based architecture. At DHIS2 we also use JSX syntax that is generally used with React.
###d2, d2-ui d2 is the DHIS2 abstraction library that allows you to communicate with the DHIS2 api in a programatic way. d2-ui is the ui component library that is build on top of d2 to allow reuse of common components that are used within DHIS2 applications. d2-ui also contains our own application wiring code through its stores and actions.
d2-ui makes use of material-ui for rendering more basic components like TextFields and Lists. It is therefore quite useful to look into this library too when building DHIS2 apps and making use of d2-ui.
Webpack is a module bundler that allows the use of plugins to do various other things. We make use of webpack for the following things:
- Bundling the files up into a single file. (The primary webpack use case)
- Transpiling ES2015 and React JSX code to ES5 syntax so it runs in the browser. (This is done using Babel.)
- Loading Scss files. Scss is a css pre-processor that has quite some fancy features as variables, nesting of style declarations etc.
- Minifying the bundled file to reduce file size
- Remove duplicate dependencies
To make the development a more interactive experience we use webpack-dev-server
to provide us with a development server that watches the project files and refreshes the browser when changes are detected.
Npm is used as both a dependency management tool as a workflow manager through its scripts
as can be seen in the package.json. It provides convenience commands to kick off various tasks. These tasks are mentioned above as npm run <command>
, npm start
, npm test
, etc.
To make sure the code is in line with the code style, we use eslint as a static style checker. To a large degree we follow the airbnb Javascript styleguide. We do however have slight modifications which are defined in our own eslint-config. (eslint-config-dhis2)
Mocha is a test runner that runs the unit tests. Chai is the assertion library that is used to do assertions within those tests. It supports various styles. At DHIS2 we generally tend to go with the expect/BDD variant. Sinon is used to do mocking within the tests and to fake HTTP requests where needed. The interesting things to look at for sinon are it's spies and stubs calls and the fakeServer.
Enzyme tool to make testing of React components easier. They provide a pretty clean api to get information from your rendered react components.