Altinn / Altinn/app-frontend-react

As an app developer, I want a better error message for the Input and Likert components

Open
#2,693 0 comments 0 reactions 0 assignees View on GitHub
area/layout area/validation kind/user-story
Dominant language
TypeScript
Stars
21
Forks
33
Avg merge
6d 23h
Merged PRs (30d)
3

Description

### Description

I came across these messages while testing component behaviours in Studio.

![Image](https://github.com/user-attachments/assets/ca976d7d-63f0-4a17-bfa1-107a64c8438b)

![Image](https://github.com/user-attachments/assets/93602111-e63d-479a-a7cd-f18dc8cf51d7)

I suggest a rewrite of the messages, to convey in plain language what the error is.

### Additional Information

Note: There might be similar messages for other components that need revision as well.

### Tasks

Input:
Style: Remove the bullet point in the first paragraph.
Change the wording of the message to:

**Det oppsto en feil for Input-8WXOK4**:
Datamodellbindingen peker mot typen object i datamodellen. Den må enten være en string, number, integer eller boolean.

Bytt type og prøv igjen for å kunne vise komponenten riktig i skjemaet.

Likert:

Det oppsto en feil for Likert-nfoXhh:
Datamodellbindingen peker mot typen string i datamodellen. Den må være array.
Bytt type og prøv igjen for å kunne vise komponenten riktig i skjemaet.

### Acceptance Criterias

Messages have better wording

Contributor guide

Open the contributing guide

Research direction

Locate the validation messages for the Input and Likert components and compare them with the exact wording requested in the issue. Update the messages so they clearly identify the component, explain the expected data-model type, and tell the user to change the type; done means both messages match the specified wording and behavior remains correct.

Written by the indexing model from the issue text.

Assessment

Tech stack
react, typescript
Domain
frontend
Issue type
Bug
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.