Feature Requests
Feature, docs and use-case samples requests for ServiceStack. If you can, focus on the end-user benefit / use-case, rather than the technical details so we can focus on the end-goal and free us to work on how best to achieve it. Features can also include supporting content, e.g. a starter project on how to use ServiceStack with another product (e.g. SS + SharePoint).
162 results found
-
Support the Oracle OrmLite provider
Currently Oracle is not a supported OrmLite provider that's listed on:
http://servicestack.net/downloadVote for this feature request if you would like to see the OrmLite Oracle provider officially supported.
36 votes -
API Explorer/Meta data enhancements
Building upon swagger feature, (but possibly re-engineering)
Support to include:
- complex (nested) DTO's and array
- markdown documentation (for detailed description)
- role/access based display (so only authorised endpoints are displayed)
- rebranding support
- ability to install nuget package without /docs folder (so as to get annotations, but not html in a model lib)84 votes -
Better request and exception logging
As it exists now, request logging only logs valid requests.
Request Logging:It does not log the request if the request is denied for Endpoint Restriction.
It does not log the request if the request is denied because a route could not be matched (say a parameter was missing, etc).
It does not log valid requests that are 'in process' - ones that request has been received, but response not sent yet.Essentially I would like to see every request sent to the service to be logged in some fashion.
As far as exceptions go, you have some pretty nice…
28 votes -
Response field filtering
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
16 votes -
Add support for expand object graph on request by default out of the box
It would be great to have the option to expand by request descendant objects indicating route or getting href attribute with route by default.
10 votes -
Support more sql math operators
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)1 vote -
Update links in Community resources
I went trough the links in chapter:
Community Resources September 20, 2015
on page:
http://docs.servicestack.net/create-webservice-from-scratchto have a look on how old the articles where. There where a number of not found:s as well as one very graphic adult nude gymnastic site...
The entries still there where a bit on the old side.Creating A Simple Service Using ServiceStack by Shashi Jeevan 11/19/2014
Introducing ServiceStack by @dotnetcurry ???????????????
Create web services in .NET in a snap with ServiceStack by @techrepublic August 5, 2014
How to build web services in MS.Net using ServiceStack by @kishoreborra July 29, 2014
Getting Started with…1 vote -
Port AspNetWindowsAuthentication To .Net Core
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
6 votes -
Expand Generic Type when documenting responses
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.
4 votes -
Silence code analysis for "Add ServiceStack reference..." generated code.
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.
1 vote -
Support change MaxLimit of query feature for specific dto
Support change MaxLimit of query feature for specific dto
1 vote -
Support sharding in sentinels mode.
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
1 vote -
Stripe Events
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.
3 votes -
ADOMD.net Orm provider addition and would work with AutoQuery
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.
6 votes -
MiniProfiler async support
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
1 vote -
Update Kotlin docs to reflect the fact that it is now supported in Android Studio by default
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
1 vote -
Update Java ServiceClient to use Route's when possible
Look at adopting approach for custom impl at:
https://github.com/ServiceStack/ServiceStack.Java/issues/205 votes -
RediSearch Client forthcoming from ServiceStack?
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!
2 votes -
Create a ss-utils.js like library that shares ServiceStack backend Validation Feature rules with AngularJs 4 Reactive Forms
Validation Rules should live in one place.
AN Angular4 component should be able to call myservice/validation and get the validation rules for front-end inline form validation. This has to be the number one most overlooked feature of any framework or stack I have ever seen.
Using the Validation Feature/Fluent Validation rules expressed on the back-end, a standard JSON response could be serialized, using reflection of the back-end POCO models and than sent to AngularJs 4 front-end, that Reactive Forms could ingest.
This front-end library should not have any dependency on jQuery and the focus should be on AngularJs Reactive Forms…
1 vote -
Group operations on metadata page by the service they are in
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.3 votes
- Don't see your idea?