#burner-front

how to start working on burner-front ?

• build the app with npm run dev
• launch some utils with gulp which handle lint and traductions

build

• npm run dev

    // this code will stay in dev mode
    if(process.env.NODE_ENV !== 'production' && storage.getItem('burner.debug')){
        console.log("123456789");
    }

• npm run prod

    // this code will be deleted in production mode
    if(process.env.NODE_ENV !== 'production' && storage.getItem('burner.debug')){
        console.log("123456789");
    }

traductions

• we handle traduction with react-intl v2

• there are two phases

  • in the build process, babel-plugin-react-intl extracts the default keys right from the code and create files which are called files of reference in ./app/langs/default (see .babelrc)
  • in the watch process, these files of reference are the entry point of scripts/traduction.js which create/merge the i18n files (like app/langs/en.json) by adding/removing the keys in the file

• At the end we just need to write the translations in app/langs/*.json

Creation d'une session

• on utilise la key 'sessionCreator' du store que l'on met à jour avec sessionCreatorUpdateSession
• voici le process d'une creation/generation, chacunes de ses actions se termine par un sessionCreatorUpdateSession
  • initializeSession
  • pushOrUpdate sur les series de la session
  • createSession

Settings

• speech
  • bénéficie d'une popup de test pour valider le bon fonctionnement. Une fois validée, elle n'apparait plus et la feature est activée
  • expect for speechFeatureDetector and speechTestResult we should avoid manipulate localStorage directly.

deployment

• ansible-playbook ansible/burner-deploy.yml --extra-vars="hosts=webservers version=master" --ask-vault

info

• firefox ne supporte pas le mp3 à cause de pb de licence