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 the following code which is somewhat straightforward to convert but the FieldDateMath type seem to have a huge gap when it comes to working with DateTimes. It's not intuitive what I should pass to new FieldDateMath().
varbounds=newExtendedBounds<DateMath>{Minimum=start,Maximum=end};// start and end are DateTime's
...new DateHistogramAggregation { ExtendedBounds =bounds};
Expected behavior
Should be able to quickly do a bounds using dates.
^ This would at least allow you to initialize the FieldDateMath with a DateTime value that is implicitly converted to DateMath. We can additionally add an implicit conversion operator from DateTime -> FieldDateMath in addition.
Currently, DateMath (which is an alias for string) incorrectly gets flattened to string:
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 the following code which is somewhat straightforward to convert but the FieldDateMath type seem to have a huge gap when it comes to working with DateTimes. It's not intuitive what I should pass to
new FieldDateMath()
.Expected behavior
Should be able to quickly do a bounds using dates.
Reference: FoundatioFx/Foundatio.Parsers#84
The text was updated successfully, but these errors were encountered: