-
Notifications
You must be signed in to change notification settings - Fork 419
New issue
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
Improve nested fields documentation #784
Improve nested fields documentation #784
Conversation
The Field Reuse section of docs was not documenting nested fields correctly. For example, if interface can be nested under `observer.ingress` and `observer.egress`, the docs would display `observer.interface.*`, instead of `observer.ingress.interface.*` and `observer.egress.interface.*`. This patch improves the docs by adding the full nesting path.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Oh, nice catch! Thanks for submitting this, @adriansr
I'll merge and backport to 1.5, to fix the public docs ASAP.
I'll also open an issue to fix this upstream in ecs_nested.yml. The nestings
array in there is now misleading, and should better capture what you've fixed for asciidoc. But fixing the docs is more pressing for now, so we'll address separately.
The Field Reuse section of docs was not documenting nested fields correctly. For example, if interface can be nested under `observer.ingress` and `observer.egress`, the docs would display `observer.interface.*`, instead of `observer.ingress.interface.*` and `observer.egress.interface.*`. This patch improves the docs by adding the full nesting path.
The Field Reuse section of docs was not documenting nested fields correctly. For example, if interface can be nested under `observer.ingress` and `observer.egress`, the docs would display `observer.interface.*`, instead of `observer.ingress.interface.*` and `observer.egress.interface.*`. This patch improves the docs by adding the full nesting path. Co-authored-by: Adrian Serrano
The Field Reuse section of docs was not documenting nested fields correctly. For example, if interface can be nested under `observer.ingress` and `observer.egress`, the docs would display `observer.interface.*`, instead of `observer.ingress.interface.*` and `observer.egress.interface.*`. This patch improves the docs by adding the full nesting path.
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.
Before:
After: