-
Notifications
You must be signed in to change notification settings - Fork 418
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
Introduction of an optional short field description #330
Conversation
6c47109
to
5f50b7e
Compare
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.
Approved with the minor fixes and changes I committed.
@dedemorton Here's @webmat 's work on toward giving us a shortdesc. |
@@ -20,7 +20,7 @@ | |||
type: keyword | |||
short: Name of the cloud provider. | |||
description: > | |||
Name of the cloud provider. Example values are aws, azure, gce, or | |||
Name of the cloud provider. Example values are aws, azure, gcp, or |
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.
Good catch
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.
Since it's my own PR, I can't mark as Approved. But I agree with your changes, Mike :-) Thanks.
I'll merge.
Also: - Replace incorrect `ec2` example in `cloud.provider` with `aws`. - Add pointer in description of `http` field set to `url` field set.
This will improve consistency with how we've been formatting field definitions.
Comes with minor description adjustments as well.
typo - "field" to "fields" in message description
There's now two fixes in the field description
55a7bd6
to
0022671
Compare
@@ -17,8 +18,9 @@ | |||
level: extended | |||
example: ec2 |
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.
@webmat Sorry I just saw this PR for some reason... Thanks for making the changes! I just found this ec2
still in provider example. This probably should be aws
instead.
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 jeez, we fixed the example in the text, but not in the example
field, haha! Thanks for pointing it out 👍
PR elastic#330 only fixed the text in the description :-)
PR elastic#330 only fixed the text in the description :-)
PR #330 only fixed the text in the description :-)
…n to fields and fieldsets (elastic#330) Additional things were fixed, while playing in these descriptions: - Some definitions were adjusted in terms of wording and in terms of separating paragraphs (double \n) - `cloud.provider` examples fixed to mention the actual provider, not a service like "ec2" - Add pointer in `http` field description to `url` - Lowercased the `log.level` examples. The field doesn't technically have the requirement, but at least we can start guiding in that direction for the future.
…elds and fieldsets (#330) (#362) Backport of PR #330 to 1.0 branch. Original message: Additional things were fixed, while playing in these descriptions: - Some definitions were adjusted in terms of wording and in terms of separating paragraphs (double \n) - `cloud.provider` examples fixed to mention the actual provider, not a service like "ec2" - Add pointer in `http` field description to `url` - Lowercased the `log.level` examples. The field doesn't technically have the requirement, but at least we can start guiding in that direction for the future.
This PR adds a
short:
description to the YAML format for defining fields. All fields who need a short description for easy display in cramped spaces now have one.This PR does not address the outputs which would benefit from this new short description. This should be addressed in a separate PR per output. PRs welcome, BTW ;-)
In reviewing all of these field descriptions, some main descriptions were adjusted as well.
A few other concerns have been addressed also:
ec2
example incloud.provider
withaws
.http
field set tourl
field set.I can extract to their own PR, if needed.
Questions