We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Elastic provides a collection of JSON files that describe the Elasticsearch HTTP API that are explicitly meant to “facilitate development of libraries and integrations”. It seems worth investigating the possibility of using those specs in Elastisch, whether for code generation (à la Carmine, which uses the official Redis command reference to generate its own command API) or something else.
The text was updated successfully, but these errors were encountered:
Sounds good.
Sorry, something went wrong.
No branches or pull requests
Elastic provides a collection of JSON files that describe the Elasticsearch HTTP API that are explicitly meant to “facilitate development of libraries and integrations”. It seems worth investigating the possibility of using those specs in Elastisch, whether for code generation (à la Carmine, which uses the official Redis command reference to generate its own command API) or something else.
The text was updated successfully, but these errors were encountered: