Lukáš Hornych

We want to support pagination of individual facet statistics within group of facet summary. Currently, all facet statistics within a group are returned every time. The problem is there may...

Right now, we don't have any standardized way of propagating changes to the C# client (also we need to think about future clients). Specifically, we want to notify developers of...

GraphQL/REST APIs allow EntityProperty constraint but evitaDB doesn't

2

We've found out that GraphQL and REST APIs allow `entityProperty` order constraint inside a `referenceProperty` constraint like [so](https://demo.evitadb.io/lab?sharedTab=N4IgLghgRgKgngBwKYgFwgOYCcIIBYCKAMgMID2AdgM5kA2KANONAAoQ4C2VaoAxpRSS8wAS0oBJACZoQkpBzIgmvCJFpkMAOQgcU6JADcRkJSBHVIFXknjIZk1RBABfJpCgARRzxABHAK5IWHAywAA6FAAEkbQiVGAsWGSS-sIAFBHR0WRYclgAQnCo4VFZ0VhIAGZBSFZIbJxIYEEAahC0gVSJZMhYYEWRJWVltaL93b39qIOZw2UV1RV1DTpNQRNBUzOlc2WqYFgiUP7NAPK5QeIUK7rNWNpg-ji00wCCAMoks7uRzt-Dfx2WUBZRBkQAlNsyghDhx2HAANJIOCzZzRCLOUwGdgiaD0bjoIaRDEuZxAA). But this throw an error because core of evitaDB doesn't support such...

Generated OpenAPI YAML/JSON has version `3.0.1` even though we use `3.1` for building `io.evitadb.externalApi.rest.api.builder.RestBuildingContext#buildOpenApi`. We also use `3.1` for serializing into YAML/JSON `io.evitadb.externalApi.rest.api.resolver.endpoint.OpenApiSpecificationHandler`. There is no mention of `3.0.1` in...

Create test including large constraint query to test translation layer for GQL/REST APIs

1

Currently, we test the translation layer from JSON query to Java query tree in: ``` evita_functional_tests/src/test/java/io/evitadb/externalApi/graphql/api/catalog/dataApi/resolver/constraint ``` but this tests only basic rules of translation, but it doesn't test if...

There is a concept of persisted queries in GQL APIs, where queries are precompiled on server and client requests queries by IDs only with custom variables. This could be help...

We are missing support for multiple reference names in `hierarchyOfReference` constraint, because there is varargs for these reference names followed by OPTIONAL enum value parameter. Problem occurs when we use...

Switching off developer tools on demand

4

Provide way to disable [introspection in GraphQL](https://www.apollographql.com/blog/graphql/security/why-you-should-disable-graphql-introspection-in-production/) and disable OpenAPI schema endpoint via configuration options.

Create GitHub pipeline for validating OpenAPI schema

2

Using GitHub action and docker, we could validate OpenAPI schemas from evitadb.io catalogs using redocly.

GraphQL supports field aliases which can lead to duplicate fields with different arguments and different sub fields. This is problem especially for extra results e.g. `facetSummary` where we support only...