Supporting component and dataModel lookups in optionFilter when using source options

[olemartinorg]

Description

After the optionFilter property was added, in an unrelated task, I saw that filtering the 'repeating group-sourced' options on the 'Pets' page in ttd/frontend-test was a perfect use-case for optionFilter. In order to filter out repeating group rows that had not been filled out yet, it was painfully obvious that the filter should support lookups per row when each option comes from a row.

So, this functionality allows this expression filter to work:

{
  "id": "hiddenPets",
  "type": "Checkboxes",
  "source": {
    "group": "Pets",
    "label": "PetName",
    "value": "Pets.UniqueId"
  },
  "optionFilter": [
    "and",
    ["notEquals", ["dataModel", "Pets.Age"], null],
    ["notEquals", ["dataModel", "Pets.Name"], null],
    ["notEquals", ["dataModel", "Pets.Species"], null]
  ]
}

This Checkboxes component will get options from the Pets repeating group, but rows where all the fields are null (Age, Name and Species) will be filtered out. I was also able to do this using the existing value function, but it's much more fiddly, brittle and difficult to work with - looking up in the data model directly is obviously better.

Also, component lookups will work as well (but only if there is a RepeatingGroup bound to the path in the data model - dataModel lookups will work regardless).

Related Issue(s)

• Forhindre gjenbruk av innhold i dropdownliste på tvers av rader i repeterende tabell #1971

Verification/QA

• Manual functionality testing
  • I have tested these changes manually
  • Creator of the original issue (or service owner) has been contacted for manual testing (or will be contacted when released in alpha)
  • No testing done/necessary
• Automated tests
  • Unit test(s) have been added/updated
  • Cypress E2E test(s) have been added/updated
  • No automatic tests are needed here (no functional changes/additions)
  • I want someone to help me make some tests
• UU/WCAG (follow these guidelines until we have our own)
  • I have tested with a screen reader/keyboard navigation/automated wcag validator
  • No testing done/necessary (no DOM/visual changes)
  • I want someone to help me perform accessibility testing
• User documentation @ altinn-studio-docs
  • Has been added/updated
  • No functionality has been changed/added, so no documentation is needed
  • I will do that later/have created an issue
    • Cleaning up and adding lots of docs about options (code lists / svaralternativer) altinn-studio-docs#1934
• Support in Altinn Studio
  • Issue(s) created for support in Studio
  • This change/feature does not require any changes to Altinn Studio
• Sprint board
  • The original issue (or this PR itself) has been added to the Team Apps project and to the current sprint board
  • I don't have permissions to do that, please help me out
• Labels
  • I have added a kind/* label to this PR for proper release notes grouping
  • I don't have permissions to add labels, please help me out

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
75.4% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[bjosttveit]

Very nice addition 🙌