Linq Queryable Decorator

Someone may know the answer to this but as we do not expose the LinqQueryable how would a consumer chain extra linq methods other than just a .Where(x => ...) clause, would we need to add some sort of extra API for this?

[mumby0168]

@IEvangelist what are your thoughts on this API?

        /// <summary>
        /// Get's an <see cref="IEnumerable{TItem}"/> collection of <see cref="IItem"/>
        /// </summary>
        /// <param name="queryBuilder"></param>
        /// <returns>A collection of item instances returned by the given LINQ <paramref name="queryBuilder"/> Cosmos SQL query.</returns>
        ValueTask<IEnumerable<TItem>> GetByQueryAsync(Action<CosmosQueryableDecorator<TItem>> queryBuilder);

This work’s nicely for the LINQ operators that result in an IQueryable<TItem> but not so much for using operators such as .Select(item => item.Id) I did kind of go down the root of the this API but then this kind of break’s the pattern of the whole Repository by now not returning a TItem this was it what do you think?

ValueTask<TReturn> QueryAsync<TReturn>(Func<CosmosQueryableDecorator<TItem>, TReturn> queryBuilder);

The API above does add a lot of complications internally to the library.

[mumby0168]

@IEvangelist what were your thoughts on this?

So this would scope the consumers to the Supported LINQ Operators, if so I like it.

Yes, that would be the plan using a wrapper similar to what I put above. I was thinking just to start with the basic ones to begin with such as OrderBy