Backport #784 to 1.5: Fix nested fields documentation #795
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.
Backport of PR #784 to 1.5 branch. Original message:
The Field Reuse section of docs was not documenting nested fields correctly.
For example, if interface can be nested under
observer.ingress
andobserver.egress
, the docs would displayobserver.interface.*
, instead ofobserver.ingress.interface.*
andobserver.egress.interface.*
.This patch improves the docs by adding the full nesting path.