Skip to content
This repository has been archived by the owner on Mar 7, 2023. It is now read-only.

[#283] [FEATURE] Ajout des acquis aux épreuves pour calculer le niveau de l'apprenant (US-360). #283

Merged
merged 27 commits into from
Apr 20, 2017

Conversation

jilljenn
Copy link
Contributor

@jilljenn jilljenn commented Feb 8, 2017

(pas encore prêt, mais c'est pour me convaincre que j'avance)

@coveralls
Copy link

Coverage Status

Coverage decreased (-1.3%) to 89.796% when pulling fa491d8 on 360-compute-level-of-assessment into e8bdbd6 on dev.

@jbuget
Copy link
Contributor

jbuget commented Feb 9, 2017

I've deployed this PR to http://360-compute-level-of-assessment.pix.beta.gouv.fr. Please check it out

@jbuget jbuget closed this Feb 15, 2017
@jbuget jbuget deleted the 360-compute-level-of-assessment branch February 15, 2017 09:28
@jbuget jbuget restored the 360-compute-level-of-assessment branch February 15, 2017 09:30
@jbuget jbuget reopened this Feb 15, 2017
@jilljenn jilljenn changed the title US-360 : Ajout des acquis aux épreuves pour calculer le niveau de l'apprenant [#283][FEATURE] Ajout des acquis aux épreuves pour calculer le niveau de l'apprenant (US-360) Feb 20, 2017
@jilljenn
Copy link
Contributor Author

Il me manque encore :

  • des tests unitaires pour getNextNode (facile) et propagateAcquix (plus coton déjà) ;
  • nettoyer un peu le corps de la fonction parce que je sens que ça va moyennement vous plaire (peut-être factoriser dans assessmentService).

@coveralls
Copy link

Coverage Status

Coverage increased (+0.5%) to 91.602% when pulling b0c95e2 on 360-compute-level-of-assessment into e8bdbd6 on dev.

@jbuget
Copy link
Contributor

jbuget commented Feb 20, 2017

I've deployed this PR to http://360-compute-level-of-assessment.pix.beta.gouv.fr. Please check it out

@coveralls
Copy link

Coverage Status

Coverage increased (+0.6%) to 91.624% when pulling 9b5ed6f on 360-compute-level-of-assessment into e8bdbd6 on dev.

@jbuget
Copy link
Contributor

jbuget commented Feb 27, 2017

I've deployed this PR to http://360-compute-level-of-assessment.pix.beta.gouv.fr. Please check it out

@jilljenn
Copy link
Contributor Author

Ça y est, on a des maths dans le JavaScript, ça ne rigole plus !

@jbuget
Copy link
Contributor

jbuget commented Feb 27, 2017

I've deployed this PR to http://360-compute-level-of-assessment.pix.beta.gouv.fr. Please check it out

@coveralls
Copy link

Coverage Status

Coverage increased (+0.6%) to 91.638% when pulling 350733b on 360-compute-level-of-assessment into e8bdbd6 on dev.

@jilljenn
Copy link
Contributor Author

Exemple : GET /api/assessments/1

estimated-level: 2.5
pix-score: 16
not-acquired: ["@rechinfo2"]
acquired: ["@support1", "@modèleEco2"]

});

describe('#derivativeLogLikelihood', function () {

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pas assez de test unitaires au vu de la complexité de la fonction. Est-ce possible de rajouter des cas de figure dans le test U?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ça calcule juste une formule. Y a pas de bête if à tester, tu lui donnes deux valeurs et il t'en renvoie une. Pas de risque d'exception. J'ai éclairci les intitulés des tests, et renommé.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Je plussoie David. Les tests, ce n'est pas que pour gérer les exceptions. Ça, ce n'est que du sucre. Le réel intérêt des tests est ailleurs :

  • aider à la conception (quand on fait du TDD)
  • documenter le code (on parle même de "documentation vivante")
  • se couvrir d'un harnais de sécurité pour refactorer, corriger et faire évoluer le code en toute sérénité / productivité

Il est plus simple de comprendre par l'exemple du code qu'en déchiffrant les méthodes et symboles utilisés.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Une formule de maths reste une formule de maths. Pour l'expliquer il faut des commentaires.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

De toute façon je ne me sers plus de ce code mais je vais m'en servir bientôt, tu veux que je supprime ?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Supprimé. Je le rechargerai lors d'une future PR.


describe('Acceptance | Application | analysis-utils', function () {

describe('#proba', function () {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"Proba" n'est pas assez explicite. Proba de quoi ?


[
{ title: 'theta equals diff', theta: 2, diff: 2, answer: 0.5 },
{ title: 'various arguments are passed', theta: Math.log(0.5), diff: 0, answer: 1/3 },
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Difficile à comprendre pour un profane.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Est-ce que quelqu'un qui s'y connaît y comprendrais quelque chose avec ces 2 cas de test ?

});

it('should return the expected assessment', function (done) {
// XXX: incomplete test, should also demonstrate that it returns the whole answer grape.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Enlever le XXX, désormais c'est bon on fait l'assertion sur toute la grappe des answers

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

le XXX est à 2 endroits, les supprimer ts les 2

_.forEach(modelAnswers, function(answer) {
if(knowledgeOf.hasOwnProperty(answer.challengeId)) {
const startNode = knowledgeOf[answer.challengeId][0];
if (answer.result == 'ok') {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pas de == en JS !! _.isEqual, ou bien ===

@coveralls
Copy link

Coverage Status

Coverage increased (+0.6%) to 94.345% when pulling 202e041 on 360-compute-level-of-assessment into f402cd8 on dev.

@jbuget
Copy link
Contributor

jbuget commented Apr 7, 2017

I've deployed this PR to http://360-compute-level-of-assessment.pix.beta.gouv.fr. Please check it out

@coveralls
Copy link

Coverage Status

Coverage increased (+0.6%) to 94.345% when pulling 6f61bd6 on 360-compute-level-of-assessment into f402cd8 on dev.

@jbuget
Copy link
Contributor

jbuget commented Apr 7, 2017

I've deployed this PR to http://360-compute-level-of-assessment.pix.beta.gouv.fr. Please check it out

@coveralls
Copy link

Coverage Status

Coverage decreased (-0.3%) to 94.361% when pulling 7e1c3f2 on 360-compute-level-of-assessment into dc50eb2 on dev.

@jbuget
Copy link
Contributor

jbuget commented Apr 20, 2017

I've deployed this PR to http://360-compute-level-of-assessment.pix.beta.gouv.fr. Please check it out

@coveralls
Copy link

Coverage Status

Coverage decreased (-0.3%) to 94.361% when pulling 9b54c29 on 360-compute-level-of-assessment into dc50eb2 on dev.

@jbuget
Copy link
Contributor

jbuget commented Apr 20, 2017

I've deployed this PR to http://360-compute-level-of-assessment.pix.beta.gouv.fr. Please check it out

@jbuget
Copy link
Contributor

jbuget commented Apr 20, 2017

Là aussi il y aura pas mal de refactoring à faire dans le futur, mais pour la santé de tous et du projet il faut avancer. On prendra le temps de refactorer de façon itérative quand on viendra à toucher le code associé #BSR.

@jbuget jbuget merged commit fc18657 into dev Apr 20, 2017
@jbuget jbuget deleted the 360-compute-level-of-assessment branch April 20, 2017 13:22
Akhilian pushed a commit that referenced this pull request Apr 20, 2017
…u de l'apprenant (US-360). (#283)

* Add knowledge (acquis) to challengeSerializer

* Add acquix to acquired / not_acquired arrays

* Add tests for assessment level estimation

* Fix tests for computing level of assessments

* Add unit tests and compute PIX score

* Fallback when history is empty or challenge has no knowledge

* Take review into account

* Rename variable

* Make a service for populating scores in assessments

* Add unit tests

* Refactor code

* Cleanup

* Extracting getScoredAssessment in the assessment service

* Refactoring ChallengeService#getKnowledgeData

* Missing semicolon on changes

* Extracting the performance statistics in a specific file + creating tests

* Lets refactor the Scoring#getPerformanceStats function

* Adding tests on Scoring#computeDiagnosis

* Refactoring #populateScore into #_completeAssessmentWithScore

* Refactoring assessmentService#getScoredAssessment and creating tests

* Introducing a 404 error when the assessment does not exist

* Renamming skill to knowledge to preserve consistency

* Add forgotten important test

* Fix test

* Refactor old for..in form into lo-dash _.forOwn
jbuget pushed a commit that referenced this pull request Apr 24, 2017
…lit avec master + MAJ de dev sur Master (#378)

* try to restore prod

* [#370] [CLEANUP] Suppression des positional params. (#370)

* Remove deprecated and unused components app-header and app-footer

* Remove positional params for component comparison-window

* Oops (forgotten .only in tests)

* Remove positional params for component challenge-statement

* Declare 'challenge' as a component property for challenge-statement

* Remove positional params for component feedback-panel

* Remove positional params for component qroc-solution-panel

* Fix tests

* On expose un nouvel endpoint avec les infos api sur /api (#375)

[#375] [FEATURE] On expose un nouvel endpoint avec les infos api sur /api (US-453).

* Changement de version 1.6.2 vers 1.6.3

* Update CHANGELOG.md

* [#283] [FEATURE] Ajout des acquis aux épreuves pour calculer le niveau de l'apprenant (US-360). (#283)

* Add knowledge (acquis) to challengeSerializer

* Add acquix to acquired / not_acquired arrays

* Add tests for assessment level estimation

* Fix tests for computing level of assessments

* Add unit tests and compute PIX score

* Fallback when history is empty or challenge has no knowledge

* Take review into account

* Rename variable

* Make a service for populating scores in assessments

* Add unit tests

* Refactor code

* Cleanup

* Extracting getScoredAssessment in the assessment service

* Refactoring ChallengeService#getKnowledgeData

* Missing semicolon on changes

* Extracting the performance statistics in a specific file + creating tests

* Lets refactor the Scoring#getPerformanceStats function

* Adding tests on Scoring#computeDiagnosis

* Refactoring #populateScore into #_completeAssessmentWithScore

* Refactoring assessmentService#getScoredAssessment and creating tests

* Introducing a 404 error when the assessment does not exist

* Renamming skill to knowledge to preserve consistency

* Add forgotten important test

* Fix test

* Refactor old for..in form into lo-dash _.forOwn

* [#372] [CLEANUP] Importation des followers dans base de données de production et suppression de scripts d'import (US-449) (#372)

* [#353][BUGFIX] Fix placement-tests HTML and route for placeholder images (#353)

[#353] [BUGFIX] Correction du rendu de la route /placement-tests (US-425).

* [#357] [FEATURE] Sauvegarder le temps écoulé pour chaque épreuve (US-361). (#357)

* New migration to add elapsed time to Answers table

* Add elapsedTime attributes in answer-serializer

* Add test to answer-controller-update

* Api is ready to receive elapsed time

* improve node version for coverage

* Update answer model

* component save time elapsed but no test added

* Fix review comments

* [#364] [INFRA] Extraction des identifiants Airtable dans des variables d'environnement (US-430). (#364)

* Add tasks to configure environment for development

* Fix build

* Remove useless description in README.md

* shutdown pretender server on app destroy (#362)

This fixes a "You created a second Pretender instance
while there was already one running" warning during
acceptance tests.

See miragejs/ember-cli-mirage#915

* de-duplicate email validation code (#361)

Use an utility function for validating email adresses (rather than a
full-blown service).

IMO Services should be used when the service is a object with several
method. In this case instantiating a service makes sense.

When the code is a simple function, an utility in `utils/` is simpler,
and involves less boilerplate.

This commit has the nice side-effect of actually simplifying the code
that uses the email validation: no need to inject a custom service,
or to define a private helper function.

* [#366] [INFRA] Correction d'avertissements dans les tests : "unsafe CSS bindings" (#366)

* progress-bar: escape CSS style

Fix a Glimmer warning about unescaped classes.

* timeout-jauge: escape CSS style

Fix a Glimmer warning about unescaped classes.

* [#360] [CLEANUP] Meilleure gestion des conditions de tests liées à l'environnement (issue #335). (#360)

* Add variable spy in config to detect if Env is test

* fix lint errors

* Fix all

* delete useless space

* Add Env variables according to theirs intents to components where they are used

* delete intestMode variable

* Attache env variables to APP context

* Fix bug en staging le timer enregistrait toujours 0 dans le temps écoulé (#369)

* [#368] [BUGFIX] Enlever le séparateur de la zone de réponse pour les QROCM (US-369) (#368)

* transform hr to br and add margin beetween inputs

* second commit to have a review app

* delete breakline for qroc which appear sometimes

* [#342] [FEATURE] Affichage de la zone de correction pour les challenges QROCM-ind (US-385) (#342)

* first commit

* create component

* ajout test intégration sur comparison window

* continuer sur box de comparaison pour QROC

* implem QROC sans les tests

* make previous tests pass

* add unit test on component qroc-answer-comparison-box

* add integration test on qroc-answer-comparison-box

* refacto jerem

* refacto

* add acceptance tests

* add acceptance tests1

* rename pour qroc-solution-panel and create qrocm solution panel

* Fix tests

* back-up for qrocm-ind

* commit to change branch

* rename component

* wip regex labels treatments

* create component qrocm-ind and first computed property

* labelstodiplay done with test, reflexion on answers to dispay

* wip

* wip reflexion comment organiser les donner à envoyer hbs

* computed property to formate the data, done and tested

* computed property done with bug

* no bug anymore, wip on dataToDisplay

* tentative avec proposalsAsBlock

* utilise le proposal block, reste à derterminer comment on connait la validité de chacune des reponse

* succeed parse des label avec ${} \o/

* basic front done mais retour du bug avec pas de grisement derrière la popin

* tentative de resolution de bug

* add unit test to computed property and about to start the html/css

* refacto computed property to facilitate css of right/wrong/no Asnwer possibility on front

* front done, il manque juste un alignement de la bonne reponse en dessous de l'input

* alignement reponse/solution done

* display only one solution on front and start integration test skull

* delete a log

* integration tests done

* refacto real unit test

* finish unit test

* fix regression sur qroc (affiche la reponse meme quand c'est bon)

* add unit test

* fix bug for qrocm passed answer and refacto computed property

* delete .only in test

* fix make tests pass

* delete comment

* computed properties of qrocm-ind passed to utils, need to be refacto

* delete comment

* delete comment

* refacto

* end of the merge

* Try to fix circle.yml for bower

* refacto 1

* adds from tech review

* regler bug benjamin sur la review app et ajout de test

* delete .only

* click sur zone grisé fait sortir de la modale + test

* test to save resultDetails done

* ajout de la propriété enabledTreatments dans le serializer airtable de solution. refacto emplacement de t1, t2 et t3 + ajout de tests pour ces fonctions. modification de applyTreatments onSolutions en utilisant les fonction t1 t2 t3, wip modification des tests de match dans solution-service-qrocmind en ajoutant le champs enabledTreatments

* refacto solution-service-qrocm-ind

* Fucking code

* Fucking code

* aaaaaaaah resolved test :)

* make tests pass after pull

* refacto tests

* Fix the fucking tests

* add save of resultDetails in dataBase

* resolve api answer serializer, implement fronts

* debut refacto, le nouveau answersAsObjects ne fonctionne pas comme on le veut avec reduce, A VOIR

* Fix the build

* Oops

* Refactor solution-services-x

* Some refactoring

* Continue to refactor

* Continue to refactor

* Continue to refactor

* Rename solution-service#match into #revalidate

* Take into account code review remarks

* delete comment and rename en camelCase

* refacto sur nom de variables test api

* continuing refacto

* refacto with pierre and florian dans qrocm ind solution panel

* gestion du cas où le challenge QROCM-ind est passé (null\n est enregistré en base)

* fix when resultdetailsYaml is null

* last change from jeremy review (!= to !==)

* delete import dir

* reactivate mailjet

* keep sqlite in package .json

* [376] [CLEANUP] Amélioration de l'image de présentation sur la page d'accueil (US-417). (#376)

* Replace index hero image by new one

* Decrease home page image height

* [#373] [BUGFIX] Affichage de l'avertissement 'epreuve timée' lorsque deux challenges du même type se suivent (US-424) (#373)

* resolve bug, about to add a test

* add acceptance test

* Restore dotenv sample file

* Refactor component to follow team standards elements of a component order

* Nouvelle version du projet : v1.7.0 (précédement v1.6.3)

* Update CHANGELOG.md

* [INFRA] Mise à jour du script pour gèrer les problèmes de conflit avec master
@jbuget jbuget modified the milestone: v1.7.0 Apr 25, 2017
jbuget pushed a commit that referenced this pull request Jul 12, 2017
…ement dédié (US-456). (#461)

* try to restore prod

* [#370] [CLEANUP] Suppression des positional params. (#370)

* Remove deprecated and unused components app-header and app-footer

* Remove positional params for component comparison-window

* Oops (forgotten .only in tests)

* Remove positional params for component challenge-statement

* Declare 'challenge' as a component property for challenge-statement

* Remove positional params for component feedback-panel

* Remove positional params for component qroc-solution-panel

* Fix tests

* On expose un nouvel endpoint avec les infos api sur /api (#375)

[#375] [FEATURE] On expose un nouvel endpoint avec les infos api sur /api (US-453).

* Changement de version 1.6.2 vers 1.6.3

* Update CHANGELOG.md

* [#283] [FEATURE] Ajout des acquis aux épreuves pour calculer le niveau de l'apprenant (US-360). (#283)

* Add knowledge (acquis) to challengeSerializer

* Add acquix to acquired / not_acquired arrays

* Add tests for assessment level estimation

* Fix tests for computing level of assessments

* Add unit tests and compute PIX score

* Fallback when history is empty or challenge has no knowledge

* Take review into account

* Rename variable

* Make a service for populating scores in assessments

* Add unit tests

* Refactor code

* Cleanup

* Extracting getScoredAssessment in the assessment service

* Refactoring ChallengeService#getKnowledgeData

* Missing semicolon on changes

* Extracting the performance statistics in a specific file + creating tests

* Lets refactor the Scoring#getPerformanceStats function

* Adding tests on Scoring#computeDiagnosis

* Refactoring #populateScore into #_completeAssessmentWithScore

* Refactoring assessmentService#getScoredAssessment and creating tests

* Introducing a 404 error when the assessment does not exist

* Renamming skill to knowledge to preserve consistency

* Add forgotten important test

* Fix test

* Refactor old for..in form into lo-dash _.forOwn

* [#372] [CLEANUP] Importation des followers dans base de données de production et suppression de scripts d'import (US-449) (#372)

* [#353][BUGFIX] Fix placement-tests HTML and route for placeholder images (#353)

[#353] [BUGFIX] Correction du rendu de la route /placement-tests (US-425).

* [#357] [FEATURE] Sauvegarder le temps écoulé pour chaque épreuve (US-361). (#357)

* New migration to add elapsed time to Answers table

* Add elapsedTime attributes in answer-serializer

* Add test to answer-controller-update

* Api is ready to receive elapsed time

* improve node version for coverage

* Update answer model

* component save time elapsed but no test added

* Fix review comments

* [#364] [INFRA] Extraction des identifiants Airtable dans des variables d'environnement (US-430). (#364)

* Add tasks to configure environment for development

* Fix build

* Remove useless description in README.md

* shutdown pretender server on app destroy (#362)

This fixes a "You created a second Pretender instance
while there was already one running" warning during
acceptance tests.

See miragejs/ember-cli-mirage#915

* de-duplicate email validation code (#361)

Use an utility function for validating email adresses (rather than a
full-blown service).

IMO Services should be used when the service is a object with several
method. In this case instantiating a service makes sense.

When the code is a simple function, an utility in `utils/` is simpler,
and involves less boilerplate.

This commit has the nice side-effect of actually simplifying the code
that uses the email validation: no need to inject a custom service,
or to define a private helper function.

* [#366] [INFRA] Correction d'avertissements dans les tests : "unsafe CSS bindings" (#366)

* progress-bar: escape CSS style

Fix a Glimmer warning about unescaped classes.

* timeout-jauge: escape CSS style

Fix a Glimmer warning about unescaped classes.

* [#360] [CLEANUP] Meilleure gestion des conditions de tests liées à l'environnement (issue #335). (#360)

* Add variable spy in config to detect if Env is test

* fix lint errors

* Fix all

* delete useless space

* Add Env variables according to theirs intents to components where they are used

* delete intestMode variable

* Attache env variables to APP context

* Fix bug en staging le timer enregistrait toujours 0 dans le temps écoulé (#369)

* [#368] [BUGFIX] Enlever le séparateur de la zone de réponse pour les QROCM (US-369) (#368)

* transform hr to br and add margin beetween inputs

* second commit to have a review app

* delete breakline for qroc which appear sometimes

* [#342] [FEATURE] Affichage de la zone de correction pour les challenges QROCM-ind (US-385) (#342)

* first commit

* create component

* ajout test intégration sur comparison window

* continuer sur box de comparaison pour QROC

* implem QROC sans les tests

* make previous tests pass

* add unit test on component qroc-answer-comparison-box

* add integration test on qroc-answer-comparison-box

* refacto jerem

* refacto

* add acceptance tests

* add acceptance tests1

* rename pour qroc-solution-panel and create qrocm solution panel

* Fix tests

* back-up for qrocm-ind

* commit to change branch

* rename component

* wip regex labels treatments

* create component qrocm-ind and first computed property

* labelstodiplay done with test, reflexion on answers to dispay

* wip

* wip reflexion comment organiser les donner à envoyer hbs

* computed property to formate the data, done and tested

* computed property done with bug

* no bug anymore, wip on dataToDisplay

* tentative avec proposalsAsBlock

* utilise le proposal block, reste à derterminer comment on connait la validité de chacune des reponse

* succeed parse des label avec ${} \o/

* basic front done mais retour du bug avec pas de grisement derrière la popin

* tentative de resolution de bug

* add unit test to computed property and about to start the html/css

* refacto computed property to facilitate css of right/wrong/no Asnwer possibility on front

* front done, il manque juste un alignement de la bonne reponse en dessous de l'input

* alignement reponse/solution done

* display only one solution on front and start integration test skull

* delete a log

* integration tests done

* refacto real unit test

* finish unit test

* fix regression sur qroc (affiche la reponse meme quand c'est bon)

* add unit test

* fix bug for qrocm passed answer and refacto computed property

* delete .only in test

* fix make tests pass

* delete comment

* computed properties of qrocm-ind passed to utils, need to be refacto

* delete comment

* delete comment

* refacto

* end of the merge

* Try to fix circle.yml for bower

* refacto 1

* adds from tech review

* regler bug benjamin sur la review app et ajout de test

* delete .only

* click sur zone grisé fait sortir de la modale + test

* test to save resultDetails done

* ajout de la propriété enabledTreatments dans le serializer airtable de solution. refacto emplacement de t1, t2 et t3 + ajout de tests pour ces fonctions. modification de applyTreatments onSolutions en utilisant les fonction t1 t2 t3, wip modification des tests de match dans solution-service-qrocmind en ajoutant le champs enabledTreatments

* refacto solution-service-qrocm-ind

* Fucking code

* Fucking code

* aaaaaaaah resolved test :)

* make tests pass after pull

* refacto tests

* Fix the fucking tests

* add save of resultDetails in dataBase

* resolve api answer serializer, implement fronts

* debut refacto, le nouveau answersAsObjects ne fonctionne pas comme on le veut avec reduce, A VOIR

* Fix the build

* Oops

* Refactor solution-services-x

* Some refactoring

* Continue to refactor

* Continue to refactor

* Continue to refactor

* Rename solution-service#match into #revalidate

* Take into account code review remarks

* delete comment and rename en camelCase

* refacto sur nom de variables test api

* continuing refacto

* refacto with pierre and florian dans qrocm ind solution panel

* gestion du cas où le challenge QROCM-ind est passé (null\n est enregistré en base)

* fix when resultdetailsYaml is null

* last change from jeremy review (!= to !==)

* delete import dir

* reactivate mailjet

* keep sqlite in package .json

* [376] [CLEANUP] Amélioration de l'image de présentation sur la page d'accueil (US-417). (#376)

* Replace index hero image by new one

* Decrease home page image height

* [#373] [BUGFIX] Affichage de l'avertissement 'epreuve timée' lorsque deux challenges du même type se suivent (US-424) (#373)

* resolve bug, about to add a test

* add acceptance test

* Restore dotenv sample file

* Refactor component to follow team standards elements of a component order

* Nouvelle version du projet : v1.7.0 (précédement v1.6.3)

* Update CHANGELOG.md

* Creating a new command to update Preview
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants