Change Details

We want to build a GraphQL endpoint that allows users to query for labels of linked entities of items Offering this as an alternative to WDQS or making multiple API calls through Action API or REST API **Acceptance criteria:** - Available through reading of an item - Response includes all the elements of the requested entity (labels, descriptions, aliases, sitelinks etc.) - Ensure that only the //labels //of linked entities (statement property, statement value items, statement qualifier and statement references) can be requested, and not everything else (for example, descriptions or subsequent statements and so on.) - Pagination is not needed ------------------------------------ - Multiple instance of one field can be added to the same request, we want to figure out if there is an upper bound here

We want to build a GraphQL endpoint that allows users to query for labels of linked entities of items Offering this as an alternative to WDQS or making multiple API calls through Action API or REST API **Acceptance criteria:** - Available through reading of an item - Response includes all the elements of the requested entity (labels, descriptions, aliases, sitelinks etc.) - Ensure that only the //labels //of linked entities (statement property, statement value items, statement qualifier and statement references) can be requested, and not everything else (for example, descriptions or subsequent statements and so on.) - Pagination is not needed ------------------------------------ - Multiple instance of one field can be added to the same request, we want to figure out if there is an upper bound here **Task breakdown**: General considerations: * create a `reuse/` domain * use the `GetItem` use case in the item resolver * create the following two CRUD use cases: * BatchGetItemLabels * takes a list of item ids and a list of label language codes to fetch * BatchGetPropertyLabels * takes a list of property ids and a list of label language codes to fetch

We want to build a GraphQL endpoint that allows users to query for labels of linked entities of items Offering this as an alternative to WDQS or making multiple API calls through Action API or REST API **Acceptance criteria:** - Available through reading of an item - Response includes all the elements of the requested entity (labels, descriptions, aliases, sitelinks etc.) - Ensure that only the //labels //of linked entities (statement property, statement value items, statement qualifier and statement references) can be requested, and not everything else (for example, descriptions or subsequent statements and so on.) - Pagination is not needed ------------------------------------ - Multiple instance of one field can be added to the same request, we want to figure out if there is an upper bound here **Task breakdown**: General considerations: * create a `reuse/` domain * use the `GetItem` use case in the item resolver * create the following two CRUD use cases: * BatchGetItemLabels * takes a list of item ids and a list of label language codes to fetch * BatchGetPropertyLabels * takes a list of property ids and a list of label language codes to fetch