Closed tjololo closed 1 year ago
Should be caught in app validation in Studio or deploy checks? Completness and consistency checks?
Slack discussion: https://altinn.slack.com/archives/C02FK32SFA4/p1669189333588629
Workaround, add empty textresourcebindings:
{
"$schema": "https://altinncdn.no/schemas/json/layout/layout.schema.v1.json",
"data": {
"layout": [
{
"id": "30558946-9d1d-4a49-898c-79d94b858e01",
"type": "Input",
"dataModelBindings": {
"simpleBinding": "melding.name"
},
+ "textResourceBindings": {},
"required": true,
"readOnly": false
}
]
}
}
Workaround good enough for now. New PDF generator will not have this issue.
Description of the bug
If a layout component eg. Input or any other component is missing textResourceBindings PDF-service fails to generate PDF and returns 500
Steps To Reproduce
Create a app with a layout like this:
Deploy app and see PDF service return http 500 response due to textResourceBindings being null.
Additional Information
No response