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
`Field`/`Fields` static factory methods and conversion operators no longer return nullable references but throw exceptions instead (`Field`) if the input `string`/`Expression`/`PropertyInfo` argument is `null`.
189
202
190
-
This makes implicit conversions to `Field` more user-friendly without requiring the null-forgiveness operator (`!`) ([read more](index.md#field-name-inference)).
203
+
This makes implicit conversions to `Field` more user-friendly without requiring the null-forgiveness operator (`!`) ([read more](index.md#5-field-name-inference)).
191
204
192
-
#### 8. `FieldValue`
205
+
#### 8. `FieldValue`[8-fieldvalue]
193
206
194
207
**Impact**: Low.
195
208
196
209
Removed `FieldValue.IsLazyDocument`, `FieldValue.IsComposite`, and the corresponding members in the `FieldValue.ValueKind` enum.
Copy file name to clipboardExpand all lines: docs/release-notes/known-issues.md
+5-1
Original file line number
Diff line number
Diff line change
@@ -5,6 +5,8 @@ navigation_title: "Known issues"
5
5
6
6
# Elasticsearch .NET Client known issues [elasticsearch-net-client-known-issues]
7
7
8
+
Known issues are significant defects or limitations that may impact your implementation. These issues are actively being worked on and will be addressed in a future release. Review the Elasticsearch .NET Client known issues to help you make informed decisions, such as upgrading to a new version.
9
+
8
10
% Use the following template to add entries to this page.
Known issues are tracked on [GitHub](https://github.com/elastic/elasticsearch-net/issues?q=is%3Aissue%20state%3Aopen%20label%3A%22Category%3A%20Bug%22).
0 commit comments