Change Details

As a follow-up to the work done in https://phabricator.wikimedia.org/T396983, we'd like to build a proof of concept for the labels of linked entities functionality in GraphQL on a publicly available wiki like beta or patch demo **Acceptance criteria: ** - For the endpoint itself, we'll limit it to a GET item/label and a GET item/statement - Ensure that the labels of linked entities are only restricted to getting labels of the corresponding entity and not everything else (for example, descriptions or subsequent statements and so on.) - Ideally the statement values can be restricted to string values and item values - The final endpoint will be exposed through a special page and if possible, check if that can also be done through GraphiQL

As a follow-up to the work done in https://phabricator.wikimedia.org/T396983, we'd like to build a proof of concept for the labels of linked entities functionality in GraphQL on a publicly available wiki like beta or patch demo **Acceptance criteria: ** - For the endpoint itself, we'll limit it to a GET item/label and a GET item/statement - Ensure that only the labels of linked entities (statement property and statement value items) can be requested, and not everything else (for example, descriptions or subsequent statements and so on.) - statement value types that must be supported: string values and item values - The final endpoint will be exposed through a special page - if possible, check if we can make it easy to try out via [GraphiQL](https://github.com/graphql/graphiql/blob/main/packages/graphiql/README.md) client on another special page

As a follow-up to the work done in https://phabricator.wikimedia.org/T396983, we'd like to build a proof of concept for the labels of linked entities functionality in GraphQL on a publicly available wiki like beta or patch demo **Acceptance criteria: ** - For the endpoint itself, we'll limit it to a GET item/label and a GET item/statement - Ensure that only the labels of linked entities are only restricted to getting labels of the corresponding entity(statement property and statement value items) can be requested, and not everything else (for example, descriptions or subsequent statements and so on.) - Ideally the- statement values can be restricted toe types that must be supported: string values and item values - The final endpoint will be exposed through a special page and - if possible, check if that can also be done through GraphiQL we can make it easy to try out via [GraphiQL](https://github.com/graphql/graphiql/blob/main/packages/graphiql/README.md) client on another special page