Open Issues Need Help
View All on GitHubAI Summary: This issue proposes enhancing the "How it Works" documentation page by incorporating visual diagrams. The current page is described as being dense with prose and code examples, and the suggestion is to adapt existing diagrams from a related blog post, potentially with minor additions like `runtime_metadata.yaml`.
Schema-driven, scalable, cloud-native, batteries-included GraphQL, backed by Elasticsearch/OpenSearch
AI Summary: Enhance the ElasticGraph project by incorporating existing field/type documentation from the schema definition API into the generated `json_schemas.yaml` file as descriptions. This will improve documentation and potentially enable better code generation by tools like json-kotlin-schema-codegen, leading to improved IDE integration and developer experience.
Schema-driven, scalable, cloud-native, batteries-included GraphQL, backed by Elasticsearch/OpenSearch
AI Summary: Improve the user-friendliness of the output from the `elasticgraph-admin` rake tasks (`clusters:configure:dry_run` and `clusters:configure:perform`). This involves handling the creation of new indices (avoiding verbose diffs), and improving the display of mapping changes (showing only added fields, not removed ones, since Elasticsearch/OpenSearch doesn't support dropping fields directly). The goal is to make the output clearer and less confusing for users.
Schema-driven, scalable, cloud-native, batteries-included GraphQL, backed by Elasticsearch/OpenSearch
AI Summary: Modify the ElasticGraph gem to include the current version in dumped schema artifacts (runtime_metadata.yaml). Upon loading these artifacts, verify that the loaded version matches the currently running ElasticGraph version, raising an error if they differ to prevent compatibility issues.
Schema-driven, scalable, cloud-native, batteries-included GraphQL, backed by Elasticsearch/OpenSearch