Jan Novotný

I'm reconsidering the original proposal and want to simplify it a bit. A new model for `ReflectedReferenceSchema` will be created. This schema will allow configuration of all the properties the...

@lukashornych https://github.com/FgForrest/evitaDB/issues/260#issuecomment-1810232735 comment was moved to separate issue https://github.com/FgForrest/evitaDB/issues/650

Basic functionality with test implemented. To be done: - [x] documentation - [x] reversed predecessors

During the discussion with @lukashornych we found out the `graphql-java` has already basic tools in place: - `graphql.schema.idl.SchemaPrinter` for creating IDL (text outputs) - `graphql.schema.diffing.SchemaDiffing` for comparison of two schemas...

Similar tool exists also for Open API: https://github.com/OpenAPITools/openapi-diff

GraphQL schema in text form will be provided on GET method for url: https://server:port/gql/catalogName/ (and the same for the GraphQL schema of evita schema and system endpoint) Open API schema...

New repository created: https://github.com/FgForrest/evitaDB-API-DiffDive This tool should - accept two schema files (the source could be combined): - file system - URL (GET, no authorisation) - HTTP PUT (upload) -...

This is a good example of checking the GraphQL backward compatibility. We can find some inspiration there @lukashornych: https://www.apollographql.com/docs/graphos/delivery/schema-checks/#operation-checks

I completely agree with your conclusions. Is there any CL tool that would also protect incompatible changes in gRPC API for evitaDB API evolution?!

I think, we just need something for our internal evitaDB CI/CD pipeline to avoid non-intentional backward incompatible changes in gRPC API. We probably don't need a tool for evitaLab /...