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
The recursive functions that walk/parse templates/mappings are a usual source of confusion and are hard to tweak when changes or new features are introduced (e.g. supporting multiple ES versions, index/alias prefixing, etc).
In the end how most people would think about this problem would be something like:
Of course any refactoring should include tests to prevent breaking existing behaviour.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
The recursive functions that walk/parse templates/mappings are a usual source of confusion and are hard to tweak when changes or new features are introduced (e.g. supporting multiple ES versions, index/alias prefixing, etc).
In the end how most people would think about this problem would be something like:
Of course any refactoring should include tests to prevent breaking existing behaviour.
The text was updated successfully, but these errors were encountered: