Delay checks for arrays of objects to 3.0.1#1496
Merged
jsoriano merged 1 commit intoelastic:mainfrom Oct 9, 2023
Merged
Conversation
Collaborator
💚 Build Succeeded
cc @jsoriano |
jlind23
approved these changes
Oct 9, 2023
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.
Several packages have been already migrated to v3 and generate arrays of objects whose fields are not correctly defined, see failures in elastic/integrations#8115.
Delay this check to 3.0.1 by now, so packages can eventually be fixed without blocking the release of Package Spec v3.