You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The definition of these fields is already provided in many cases by ecs@mappings, and its definition doesn't grant that they are correctly used, this can be only checked with system tests. Current implementation forces packages developers to include this boilerplate fields.
So maybe we should remove the expectation on these fields from the spec, and ensure that elastic-package can detect misuses or absence of these fields.
The text was updated successfully, but these errors were encountered:
We currently check at the spec level that some fields are required, here:
package-spec/code/go/internal/validator/semantic/validate_required_fields.go
Lines 14 to 25 in 5325b7e
The definition of these fields is already provided in many cases by
ecs@mappings
, and its definition doesn't grant that they are correctly used, this can be only checked with system tests. Current implementation forces packages developers to include this boilerplate fields.So maybe we should remove the expectation on these fields from the spec, and ensure that
elastic-package
can detect misuses or absence of these fields.The text was updated successfully, but these errors were encountered: