Generation errors, design analysis

[romaintailhurat]

As previously described, we want to provide to users a clearer message when an error occurred during the generation phase.

Before we actually work on this issue, an analysis must be done in order to understand what should be done and where:

• at the Pogues level, before we communicate to the Eno API ?
• at the Eno API level, and therefore in Pogues to display in return a proper error message ?
• what about errors only happening at the questionnaire side (ie not raised by Pogues and / or Eno) ?

[romaintailhurat]

After debating, we will work on the problem through two issues:

1. in Pogues, check if a variable used in a control is declared
2. in Pogues again, catch a 500 status code from the Eno API in order to display a readable error message.

[ORogel]

Some random thoughs:

• an API taking more than 5 minutes to answer should not be a thing
• we need to catch as many errors as possible before the call to Eno
• maybe we could generate only a diff of the questionnaire in order to act quicker
• we should have a versionning system for questionnaire
• some changes in Eno are necessary if we want more detailled errors