internal/fields: fix handling of numeric keyword fields in arrays - #1746
Merged
Conversation
Currently, the keyword validation check does not allow for the existence of arrays of numbers. Add that support.
Contributor
💚 Build Succeeded
cc @efd6 |
Contributor
|
test integrations |
jsoriano
approved these changes
Apr 3, 2024
Contributor
|
Thanks! |
Contributor
|
Created or updated PR in integrations repository to test this version. Check elastic/integrations#9514 |
This was referenced Apr 3, 2024
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
3 participants
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.
Currently, the keyword validation check does not allow for the existence of arrays of numbers. Add that support.
Please take a look.