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:
We had code in Foundatio.Parsers that merged code mappings with server side mappings and we found a case where coded properties could be null but have a clr name and we used it for that. Is there a good way to replace this?
// coded properties sometimes have null Name propertiesif(fieldMapping.Name ==null&& fieldMapping is IPropertyWithClrOrigin clrOrigin && clrOrigin.ClrOrigin !=null)
fieldMapping.Name =new PropertyName(clrOrigin.ClrOrigin);
Elastic.Clients.Elasticsearch version: 8.15.6
Elasticsearch version: 8.15.1
.NET runtime version: 8.x
Operating system version: Any
Description of the problem including expected versus actual behavior:
We had code in Foundatio.Parsers that merged code mappings with server side mappings and we found a case where coded properties could be null but have a clr name and we used it for that. Is there a good way to replace this?
https://github.com/FoundatioFx/Foundatio.Parsers/blob/main/src/Foundatio.Parsers.ElasticQueries/ElasticMappingResolver.cs#L124-L126
Expected behavior
Being able to resolve coded properties using the clr name.
Reference: FoundatioFx/Foundatio.Parsers#84
The text was updated successfully, but these errors were encountered: