As per this example: http://www.vinaysahni.com/best-practices-for-a-pragmatic-restful-api#limiting-fields

It would be useful to be able to restrict the returned fields provided by the response.

Using a dot notation we could filter any nested properties as well. e.g.

GET /customers/fields=id,name,address,address.postcode,address.line1

It would be great to have the option to expand by request descendant objects indicating route or getting href attribute with route by default.

Extend https://github.com/WBPuge/ServiceStack.OrmLite/blob/master/src/ServiceStack.OrmLite/Expressions/Sql.cs
to support following sql math operators:
Sign
Abs
Floor
Ceil/Ceiling
Round(x, y)

At present, the AspNetWindowsAuthentication is not supported in .NET Core. ASP.NET Core does allow for Windows Authentication (through IIS reverse proxy), so it would be great to have support for this in ServiceStack.

I made an attempt at porting it myself, and it kind of works, though I'm sure I'm missing some subtleties on how it works, as I sometimes get "header already set" errors on some requests. In case this never gets picked up, here's a gist of my attempt:

https://gist.github.com/darkonejr/7bcdcf7aea9fee7d21329fd58de5d43d

We have an application that always return an AppContentResponse<T>. AppContentResponse contains some properties that are present in every response of every method we have, while the T is the actually Type of the response.

When we look at the metadata documentation, ServiceStack generates the documentation for AppContentResponse<T> without also documenting T. The strange thing is that if I create a class that actually implements AppContentResponse<TypeOfThatResponse>, both types get automatically documented.

I filed an issue at https://forums.servicestack.net/t/expand-generic-type-when-documenting-responses/5676 if you are looking for more details.

The generated code does not conform to company rules so I get a bunch of useless warnings when I run code analysis on my solution.

Just adding a

// <auto-generated>
// This code was generated by ServiceStack.
// </auto-generated>

block above or below the /* Options: */ block would be enough to exclude the generated file from code analysis.

Support change MaxLimit of query feature for specific dto

I didn't find support of client side sharding with sentinels in your Redis API. It will be a nice to have feature. I asked this question on stackoverflow, if you have some solution for the problem, it would be great to hear: https://stackoverflow.com/questions/50107173/servicestack-redis-is-sharding-supported-in-sentinel-mode

The ServiceStack Stripe library currently doesn't support retrieving of Stripe Events. It would be nice to have this feature especially when working with webhooks.

As it currently stands, I either have to install both the Stripe.net and ServiceStack.Stripe packages in my project, or switch to using just the Stripe.net package.

ADOMD.net Cubes as a source of data. I think this would be huge in adding a provider to the mix and utilize Analysis Service cubes to return faster data/query's for warehouse service use.

Some older release notes https://github.com/ServiceStack/ServiceStack/blob/net40/docs/2015/release-notes.md states that Mini Profiler async support is there, but unless I am missing something, using v5.0, I cannot get it to work. Looking at ProfiledCommand, it does not actually overload the async overloads and call IDbProfiler methods.

MiniProfiler integrated this last februari: https://github.com/MiniProfiler/dotnet/commit/8973afb7bd418a37ce38e0805dc3636942ea7788

http://docs.servicestack.net/kotlin-add-servicestack-reference should be updated to reflect the fact that Google now provides first class support for Kotlin in the IDE

Look at adopting approach for custom impl at:
https://github.com/ServiceStack/ServiceStack.Java/issues/20

I was just reading about the Redis Labs new RediSearch product for use in implementing a search engine in Redis. I saw in the RediSearch product page that StackExchange has a C# client for this product. Do you plan to implement RediSearch client in ServiceStack.Redis? I prefer ServiceStack modules to StackExchange.

If this is your roadmap, can you project delivery of such a client?

Keep up the good work! Thanks!

By default the metadata page could group the operations by the service they are in.
All user operations under UserService.
Order operations under OrderService.
etc.

The API request logger logs all fields and there is now way to disable any of them. Specifically, logging the users cookie each time takes up a huge amount of space and also makes the display difficult to use. Please add a config option to allow control over which fields get logged.

I believe we can retrieve specific versions of a file via the versionId querystring using VirtualFiles.... however VirtualFiles.WriteFile returns null so we cannot retrieve the x-amz-version-id header. It would be nice if the headers were in the response of VirtualFiles.WriteFile so we could retrieve that.

To MsgPack was really comfortable as JSON, you must add the possibility of setting "Map" mode. This will give more compatibility when migrating from one version to another, when service is updated, but clients have not yet had time.