Invalid repo configuration results in viewport list not showing up.

Description

If a viewport is saved and the repository configuration is invalid in that it references non-existent properties, saving succeeds, but when the viewport list in the admin UI is loaded, resolving the property and hence the entire REST call fails and the list remains empty.

Environment

None

Assignee

Unassigned

Reporter

Sync User [K15t]

Labels

Participants

None

Deployment

None

Time tracking

4h

Components

Sprint

None

Fix versions

Configure