Description

Today we are fetching all optionLists from backend in a singel request. If one of them is in an invalid format, the whole request will fail and you will not be able to view the content of any of the lists.

We should add a query useOptionListQuery.ts that will use the endpoint for fetching a specified optionList based on a given optionListId.

In the places where we use the query today we should adapt it like this:

In OptionListEditor.tsx:
This component is already receiving the optionListId so we can simply replace the query and pass the id to the new hook. Then a potential error from this query in this component, will be handled correct as it is implemented today.

In AppContentLibrary.tsx:
We should adapt the code list implementation to take all optionListIds as the incoming data and a onGetCodeList callback to fetch the singel code list when we need it. This way we will only get valid option lists to render and show an error per individual codeList.

In ExportForm.tsx:
We should keep the fetch all query in order to use it in this component and accept that the exported form will not have any lists if the api call fails due to a single faulty code list. This functionality is developed along with the needs of a single customer and hidden behind a feature flag.