[FEATURE] Make fluent creation of Terms query simpler

[stevejgordon]

See this discuss issue for context. Due to the specification and code generation of types, constructing a terms query for a set of long values is more complex than we would like. We should look at improving this either with additional generated code or by adding manual code for conversions from common sets of FieldValues.

[DR9885]

Having same issue. Using temporary workaround:

    public static class ElasticQueryExtensions
    {
        public static TermsQueryDescriptor<TDocument> Terms<TDocument>(this TermsQueryDescriptor<TDocument> query, long[] objs) => TermSelect(query, objs, FieldValue.Long);
        public static TermsQueryDescriptor<TDocument> Terms<TDocument>(this TermsQueryDescriptor<TDocument> query, double[] objs) => TermSelect(query, objs, FieldValue.Double);
        public static TermsQueryDescriptor<TDocument> Terms<TDocument>(this TermsQueryDescriptor<TDocument> query, string[] objs) => TermSelect(query, objs, FieldValue.String);
        public static TermsQueryDescriptor<TDocument> Terms<TDocument>(this TermsQueryDescriptor<TDocument> query, bool[] objs) => TermSelect(query, objs, FieldValue.Boolean);

        private static TermsQueryDescriptor<TDocument> TermSelect<TDocument, TValue>(TermsQueryDescriptor<TDocument> query, TValue[] objs, Func<TValue, FieldValue> selector)
        {
            var items = objs.Select(selector).ToArray();
            return query.Terms(new TermsQueryField(items));
        }
    }

Please fix soon.

[niemyjski]

+1, this would be useful