Resizing: clearer modeling in pairwise case

[nsenave]

Feature Description

The current modeling for a resizing entry asociated with a pairwise links component is like this:

{
  "resizing": {
    "FIRST_NAME": {
      "sizeForLinksVariables": [
        "count(FIRST_NAME)",
        "count(FIRST_NAME)"
      ],
      "linksVariables": ["LINKS"]
    }
  }
}

The current modeling of the sizeForLinksVariables property is a bit flawed. The response associated with a pairwise links component is a two-dimension array, so it must contains exactly 2 elements.

Use Case

This current modeling could cause issues since nothing prevents users from setting and array with 1, 3 or more elements in the source json.

Proposed Solution

I suggest something clearer like:

{
  "resizing": {
    "FIRST_NAME": {
      "sizeForLinksVariables": {
        "xAxisSize": "count(FIRST_NAME)",
        "yAxisSize": "count(FIRST_NAME)"
      },
      "linksVariables": ["LINKS"]
    }
  }
}

Note: For now, only one pairwise component per questionnaire is authorized, so we also might want to change "linksVariables": ["LINKS"] into "linksVariable": "LINKS".
Yet it feels much less necessary to me since current modeling isn't harmful, and this rule could change someday.

Alternatives Considered

Additional Context

Priority

• Low

Attachments

Related Issues

Issue to be created in Lunatic-Model, and then in Eno to use the new modeling.