-
Notifications
You must be signed in to change notification settings - Fork 17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Dynamic Unit on InputNumber #695
Comments
As mentioned in previous issues, i would prefer to have in this case an exclusive path, like a switch button for choosing between static and dynamic measure units? But most importantly, if we allow for dynamic, what is the use for a static unit list? Most designers would just use the dynamic option and write whatever they like as units. 🤔 So probably having dynamic measure units means deleting static ones, maybe at the expense of harmonization. |
Currently in jsonPogues, unit is actually an url, used in transformation to ddi for getting the value of the unit.
If we want to make the difference between VTL expression or url (that leads to a different transformation), we need to change Pogues-Model Then, in ddi, we do have
We cannot directly give the expression in <r:MeasurementUnit> |
Modélisation:
ou
|
Because of DDI modelisation, for dynamic unit we must save as value the id of a variable. |
Pour gérer l'identification du caractère dynamique de l'unité : ajout de : Pour gérer le fait que Unit pour désormais soit contenir une Uri vers RMéS, soit un nom de variable entre $ : |
need to update the saved variable in pogues-json when unit is dynamic (for ddi consideration) : |
finally we can directly use VTL field and save the content directly in Unit |
ToDo
Eno : InseeFr/Eno#715
Lunatic: InseeFr/Lunatic#668
The text was updated successfully, but these errors were encountered: