@@ -22,28 +22,28 @@ This release includes the following breaking changes:
22
22
23
23
The `Core.MSearchTemplate.RequestItem` type has been renamed to
24
24
`Core.MSearchTemplate.SearchTemplateRequestItem`. It no longer derives from the
25
- `Union<T1, T2>` type. It has been manually designed to support serialisation to
25
+ `Union<T1, T2>` type. It has been manually designed to support serialization to
26
26
NDJSON, as required by the MSearchTemplate endpoint.
27
27
28
28
The `MultiSearchTemplateRequest.SearchTemplates` property has been updated to
29
29
use this newly defined type.
30
30
31
31
This breaking change has been included in this patch release due to the
32
- original code-generated type not functioning correctly and therefore we have
32
+ original code-generated type functioning incorrectly, and therefore, we have
33
33
determined that this should ship ASAP.
34
34
35
35
[discrete]
36
36
==== MultiSearch type changes
37
37
38
38
The `Core.MSearch.SearchRequestItem` type has been sealed for consistency with
39
- the design choices in the rest of the client. While technically breaking, we
40
- have decided that this should be included in this release before any potential
39
+ the design choices of the rest of the client. While technically breaking, we
40
+ have decided that this should be included in this release before any potentially
41
41
derived types may exist in consuming applications.
42
42
43
43
[discrete]
44
44
==== Sealing union types
45
45
46
- Code-generated types derived from `Union<T1, T2>` where incorrectly unsealed.
46
+ Code-generated types derived from `Union<T1, T2>` were incorrectly unsealed.
47
47
While technically breaking, we have decided that these should be sealed in this
48
48
patch release before any potential derived types may exist in consuming
49
49
applications. Sealing types by default aligns with our broader design choices
0 commit comments