Make fields in uses cases which are not in ECS italic #55
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.
Some of the existing use cases contain fields which are not in ECS. Also we had several fields commented to make it clear they are not in ECS. In recent discussions it popped up that it could be useful for others to share their schema they use for specific use cases + the fields which are not in ECS. As we now show the fields different this is possible.
I plan to do follow up PR's to also clean up the use cases. Some are outdated and should be updated to use ECS fields, others can be useful for inspiration on new fields. Reviewing use cases is now much easier as it is directly visible which fields come from ECS and which ones not.
Additional changes