Validate expected fields normalization#765
Merged
jsoriano merged 7 commits intoelastic:mainfrom Sep 7, 2022
Merged
Conversation
Collaborator
Member
Author
|
|
Member
Author
|
Blocked till we have some way of disabling checks per package (see #615 (comment)). |
16 tasks
Collaborator
🌐 Coverage report
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
ECS fields can include normalization rules, indicated by the
normalizeparameter.By now only the
arrayrule exist, that indicates that values should be included in thefield as an array, even if there is a single element.
Validate this on test results for packages with
format_version>=2.0.0.Things to check in this review:
elastic-package.event.categoryandevent.typeto arrays as for this PR.Part of #615 and elastic/package-spec#399.