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
It looks like re-running the ECS .NET generator has picked up a change to registry.data.strings.
In 1.4.0 it was manually overridden to emit a string[] type but is now emitting string type as the field has no normalize->array definition.
The description for this property reads as:
Content when writing string types.Populated as an array when writing string data to the registry. For single string registry types (REG_SZ, REG_EXPAND_SZ), this should be an array with one string. For sequences of string with REG_MULTI_SZ, this array will be variable length. For numeric data, such as REG_DWORD and REG_QWORD, this should be populated with the decimal representation (e.g "1").
It looks like re-running the ECS .NET generator has picked up a change to
registry.data.strings
.In
1.4.0
it was manually overridden to emit astring[]
type but is now emittingstring
type as the field has no normalize->array definition.The description for this property reads as:
https://github.com/elastic/ecs-dotnet/blob/8cfe5f6c5661427204e42891ede4d8fcc8889231/src/Elastic.CommonSchema/Types.Generated.cs#L3514
Should this be modelled as an array? I was also wondering if it would be equally valid for this to be a
Union<string[], decimal>
?The text was updated successfully, but these errors were encountered: