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
Description of the problem including expected versus actual behavior:
The Nest driver used to support mapping nested objects fluently using generics
e.g. descriptor.Nested<SomeType>(n => n.Name(s => s.ListOfSomeType).Properties(s => s.Keyword(k => k.SomePropertyOfSomeType)))
Have I just overlooked how this should be done in the new driver, I have seen other tickets where people mention working around it by using the existing Nested method but using .First().SomePropertyOfSomeType all over the place ?
The text was updated successfully, but these errors were encountered:
It might be worth adding overloads for the nested mappings.
We sadly lost a bit of convenience here and there with the new auto-generated client. Auto mapping is something still on my todo list as well. I'll review this nested mapping case when I finally have time to work on this part.
flobernd
changed the title
Nested mappings no longer support generics nicely?
Feature: Push down generic types when mapping nested properties
Feb 11, 2025
Elastic.Clients.Elasticsearch version: 8.*
Elasticsearch version: 8.*
.NET runtime version: 9
Operating system version: Windows 11
Description of the problem including expected versus actual behavior:
The Nest driver used to support mapping nested objects fluently using generics
e.g.
descriptor.Nested<SomeType>(n => n.Name(s => s.ListOfSomeType).Properties(s => s.Keyword(k => k.SomePropertyOfSomeType)))
Have I just overlooked how this should be done in the new driver, I have seen other tickets where people mention working around it by using the existing
Nested
method but using.First().SomePropertyOfSomeType
all over the place ?The text was updated successfully, but these errors were encountered: