Skip to content
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

Merged
merged 3 commits into from
Mar 23, 2020

Conversation

adriansr
Copy link
Contributor

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.

Before:

Screenshot 2020-03-13 at 16 33 18

After:

Screenshot 2020-03-13 at 16 38 33

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.
@adriansr adriansr requested a review from webmat March 23, 2020 09:54
Copy link
Contributor

@webmat webmat left a 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.

@webmat webmat merged commit e306661 into elastic:master Mar 23, 2020
webmat pushed a commit to webmat/ecs that referenced this pull request Mar 23, 2020
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.
@webmat webmat added the bug Something isn't working label Mar 23, 2020
webmat pushed a commit that referenced this pull request Mar 23, 2020
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
webmat pushed a commit to webmat/ecs that referenced this pull request Mar 23, 2020
webmat pushed a commit to webmat/ecs that referenced this pull request Mar 23, 2020
webmat pushed a commit that referenced this pull request Mar 26, 2020
webmat pushed a commit to webmat/ecs that referenced this pull request Mar 26, 2020
webmat pushed a commit that referenced this pull request Mar 26, 2020
dcode pushed a commit to dcode/ecs that referenced this pull request Apr 15, 2020
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.
dcode pushed a commit to dcode/ecs that referenced this pull request Apr 15, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working documentation review
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants