Vedleggskomponent - valgfri

[hanneline]

Describe the bug

Vedleggskomponenten står med valgfri etter ledeteksten. Men det er ingen steder vi kan sette om filvedlegg er valgfritt eller ikke. På komponenten kan man sette maks antall filer, men ikke minimum.

Expected behavior

Mulig å sette at det må leveres filvedlegg, og evt et minste antall.

Screenshots

Additional info

Windows 10 Pro, Chrome

Fix

We should add an input field with minimum number of attachments uploaded. If this value is more than 0, the attachment component is required by the end user and if the value is 0 the "valgfri" label should be applied to the component. A hard validation needs to be implemented in the application stopping the end user from continuing if they have not uploaded enough attachments. Default value for max and min number of attachments should be 1.

Acceptance criterea

• Add an input field with "minst antall vedlegg" as label.
  • Size of this input field should be the same as "maks antall vedlegg"
  • Default value of this field should be 1.
• If the value of this field is 0 the "valgfri" label should be visible for the end user on the attachment component.
• If the user didnt upload enough attachments in regards to the "minst antall vedlegg" value they should get a validation message when they try to submit the form.
  • This validation message should contain how many attachments the user has to upload to reach the value. Example: "Du må laste opp 1 vedlegg for å fortsette".
• For now we dont have any validation in the UI-editor, and that means we cant stop the user from setting the minimum value higher then the maximum value. This should be solved by Hard validations in the UI-editor (to stop or guide a app developers making stupid mistakes) #1841

Sketch

UI-editor
https://www.figma.com/file/O7Oqx6p9ZUZBt8DFBNanrymh/MVP-2-Altinn-Studio?node-id=1262%3A14124

Application
https://www.figma.com/file/O7Oqx6p9ZUZBt8DFBNanrymh/MVP-2-Altinn-Studio?node-id=1465%3A0

[trymen]

Tested all acceptance criteria (Can confirm setting a max number lower than min crashes in runtime), testcafe tests on vedlegg has been updated to catch this case. Closing this issue as fixed.