Hard validations in the UI-editor (to stop or guide a app developers making stupid mistakes)

[Febakke]

Description

As an app developer I need to know that the settings are considered to be invalid.

In the future there might be quite a few combinations of settings, so we need to decide in general how to handle these situasjons, to help the service developer create the best service that they can.
(stopping them might limit them, not giving them anything might frustrate them)

An example is to set max allowed file size in the attachment component to 0 MB. We need to implement this functionality to stop the user from entering invalid settings.

Examples of service developers that has been confused: #1762, #1763 and #1560

Over time it has been introduced different types of validation messages in our studio solution. We should map out how bad this is and make a scaleable solution that can be used across all pages of our studio.

Screenshots

Screenshots or links to Figma (make sure your sketch is public)

Considerations

Input (beyond tasks) on how the user story should be solved can be put here.

Acceptance criteria

Tasks

• Introduction meeting with developers. Expose technical considerations early in the prosess and start low-resolution sketching with the developers in the meeting.
• Evaluate if a full stop or guide the developer is the best way going forward.
• Design
• QA/review with developers

[nkylstad]

Closing this issue as stale. Validation scenarios will be covered by #10425