Altinn / Altinn/app-frontend-react

As an app developer I want descriptive warnings when I'm missing textResourceBindings

Open
#318 3 comments 0 reactions 0 assignees View on GitHub
kind/user-story status/draft
Dominant language
TypeScript
Stars
21
Forks
33
Avg merge
6d 23h
Merged PRs (30d)
3

Description

### Description

When developing an application, and my app is missing the expected `textResourceBindings` as should be defined in my form layout file, the app can in some circumstances end up with the dreaded 'unknown error occurred'. Instead of getting a show-stopping error message with a cryptic trace in the console, I'd rather have the frontend tell me which component is missing which key in `textResourceBinding`, in some way. Preferably directly in the UI, or at least in the browser console.

For some components where the binding key is optional, I'd possibly prefer a weaker warning/info message in the browser console telling me about this possible problem, without showing that warning in the app user interface.

### Additional Information

[Background/discussion on Slack](https://altinndevops.slack.com/archives/CDU1S3NLW/p1656407853828659)

### Tasks

_No response_

### Acceptance Criterias

_No response_

Contributor guide

Open the contributing guide

Research direction

The issue names no files, tests, or entry points. Start by locating where frontend components resolve textResourceBindings and where missing bindings become the unknown error; done means missing required bindings identify the component and key, while optional bindings produce an appropriate console warning or info message.

Written by the indexing model from the issue text.

Assessment

Tech stack
react, typescript
Domain
frontend
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.