feat(TextResources): add support for defaultValue in variables in tex…

[mikaelrss]

Description

This PR adds support for a defaultValue option in variables in text resources. This would allow for app developers to provide a value to print if the variable points to a null-value in the datamodel. The current behavior is that the app displays the path to the datamodel.

Related Issue(s)

• closes Add defaultValue option to variables in text #1440
• does not close but can solve issue Variables in text. Empty variables in will display path to datasource. #754

PR in storage:

• feat(TextResource): add defaultValue to TextResourceVariable altinn-storage#257

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 Add documentation for defaultValue in text variables altinn-studio-docs#1134
  • No functionality has been changed/added, so no documentation is needed
  • I will do that later/have created an issue
• 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

[olemartinorg]

I'm assuming this relies on #1444 to be merged? In that case we should wait until the v3 branch is made (and the last big minor version of v3 is released this week) before we merge this.

[mikaelrss]

I'm assuming this relies on #1444 to be merged? In that case we should wait until the v3 branch is made (and the last big minor version of v3 is released this week) before we merge this.

Yes, definitely. It's got the branch of #1444 as base. But it can be reviewed already.

[olemartinorg]

Looks good! We should include config for this in frontend-test those places we know of, so that Percy picks it up in screenshots.

[olemartinorg]

@mikaelrss #1444 has been merged - maybe this should be rebased against main? 🙏

[mikaelrss]

Yeah. I'll fix it!

[sonarqubecloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
1 Code Smell

20.0% Coverage
0.0% Duplication