You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The use of VTL in questionnaire must be streamlined and stabilised throughout the softwares.
This goal includes:
streamline the use of conditions: in Pogues, we describe the display condition, but Lunatic is handling a hide condition, thus Eno adds a not operator to every condition written in Pogues.
the best way to handle this is to only handle display condition (hence, no more extra negation)
simplifiy the use of variables: for historic reasons, a $ sign is added at the beginning and the end of a variable name, but really this is only mandatory for controls and not for label.
ideally, we would like to get rid of this dollar sign that is not part of VTL
modify the input number fields to produce VTL NUMBER type: currently, when a scalar response is of number type, a string is returned, designers have to handle this discrepancy (using the cast function).
it seems reasonable to return a numeric value to VTL expression, it is only a small evolution in Lunatic.
in Pogues, streamline VTL expression: some expression are between quotes, some are not.
@JulienCarmona , @lailabent ou @AnneHuSKa
Très bonne idée ça, mais si vous pouvez commencer déjà à dire ce que vous souhaitez comme contrôles sur ce qu'on peut faire (règle VTL, variables, filtres, contrôles, séquence, rond-point, etc...).
J'ai un p'tit projet en tête (api de contrôle de ce que le concepteur a saisie pour commencer)
C'est l'étape 1. de la refonte "petit à petit" 😎
Business case
The use of VTL in questionnaire must be streamlined and stabilised throughout the softwares.
This goal includes:
display
condition, but Lunatic is handling ahide
condition, thus Eno adds anot
operator to every condition written in Pogues.display
condition (hence, no more extra negation)$
sign is added at the beginning and the end of a variable name, but really this is only mandatory for controls and not for label.NUMBER
type: currently, when a scalar response is of number type, a string is returned, designers have to handle this discrepancy (using thecast
function).Stack
DDI
Pogues
Eno
link to project issues
Lunatic
link to project issues
Progress
describe progress
Release date
here we want to keep track of deadlines; and provide links to milestones
The text was updated successfully, but these errors were encountered: