Cherry-pick #15742 to 7.x: Fix indentation in fields definition of generic modules#15755
Merged
jsoriano merged 1 commit intoelastic:7.xfrom Jan 23, 2020
Merged
Cherry-pick #15742 to 7.x: Fix indentation in fields definition of generic modules#15755jsoriano merged 1 commit intoelastic:7.xfrom
jsoriano merged 1 commit intoelastic:7.xfrom
Conversation
Remove spurious strings in fields definitions of generic modules caused by how these yaml files are indented and concatenated. (cherry picked from commit 4f0d0d7)
mtojek
approved these changes
Jan 22, 2020
kaiyan-sheng
approved these changes
Jan 22, 2020
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Cherry-pick of PR #15742 to 7.x branch. Original message:
What does this PR do?
Remove spurious strings in fields definitions of generic modules caused by how these yaml files are indented and concatenated
Why is it important?
To remove spurious content from docs and avoid unexpected issues in future changes in these fields files.