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
-
Encrypted messaging javascript client
We have message-level encryption and the corresponding .Net client library to use it. But I'd love to be able to call encrypted services from JavaScript. Ideally add to ss-utils.js, or because the encryption can get bulky, into a new ss-encrypt-utils.js.
8 votes -
AutoQuery Azure DocumentDB Data Source
Azure DocumentDB should be added among existing AutoQuery data source.
19 votes -
Allow Abstract Validators where generic is an Interface to run as part of request cycle.
When creating a validator class that extends AbstractValidator<T>, the generic must be a concrete class for the validation to actually run once that validator is registered. It would be nice if I could define several interfaces for my messages that I want specific shared validation run against, and then just register a validator for that interface, and have the validation run against any message that comes in that implements that interface.
I know there are ways to do this through request filters, as well as through attributes on the messages, but the attributes requires having to pull more dependencies into…
4 votes -
Localize Login redirect
our site has the following route format: /[Locale]/RestOfPath
The problem is that the redirect url always redirects to /Login instead of /[Locale]/Login. Could you turn AuthenticateAttribute.DoHtmlRedirectIfConfigured into a static Func instead of a static method so it is overridable?
1 vote -
auto update http://github.servicestack.net/
http://github.servicestack.net/ss_admin/autoquery/QueryRepoCommits
seems not to be updated since 2015-09-26. Maybe put an auto pull on the git repos behind it?
1 vote -
Add an LDAP Authentication Provider
With .NET Core not initially having support for Windows Authentication using the System.Directory assemblies, I would like to request the addition of a new LDAP Authentication Provider based on the Novell.Directory.Ldap.NETStandard (https://github.com/dsbenghe/Novell.Directory.Ldap.NETStandard) project. This will allow developers to update to the latest ServiceStack while still providing a way to authenticate and authorize against a legacy/non-Azure Active Directory.
24 votes -
support caching in java AndroidServiceClient
Using servicestack client in mobile development with Xamarin gives so much benefits and caching dramatically improves performance and user experience.
It would be nice to have same caching support for all clients (.NET, JAVA, ..)3 votes -
Redis Cache value compression
Redis and clients are typically IO bound and the IO costs are typically at least 2 orders of magnitude in respect to the rest of the request/reply sequence. Smaller payloads will give you higher throughput and lower latencies.
The ICacheClient interface should provide an option to enable compression. This will store a compressed string representation in the cache store (except in memory). Default should be false.
Some interesting reads:
http://stackoverflow.com/questions/6556631/compressing-strings-before-putting-them-in-redis-does-it-make-sense
http://stackoverflow.com/questions/10909602/does-redis-db-has-built-in-compression-option2 votes -
Optionally decorate DTO's with OrmLite attributes
For very small Xamarin Applications, it makes sense to use the same data models in the App as in the API backend.
This could easily be achieved, if the OrmLite attributes such as [PrimaryKey], [Unique] and so on are exposed.
This would of course be an opt-in behaviour, because by default those attributes are for internal usage.1 vote -
support F# data type for serialization and deserialization
This is specially for option type and discriminated unions. Currently it is not supported by Servicestack.Text. It would be great to have support for that.
For
type City = Abad | Pune
[<CLIMutableAttribute>]
type Person = {
FirstName:string
LastName: string option
City : City
}let p1 = {FirstName = "Foo"; LastName = Some "Bar"; City = Pune}
let jss = new JsonStringSerializer()
let p1Str = jss.SerializeToString(p1)It is serializing
"{"FirstName":"Foo","LastName":{"Value":"Bar"},"City":{"Tag":1,"IsAbad":false,"IsPune":true}}"Where is should be
"{"FirstName":"Foo","LastName":"Bar","City":"Pune"}"For reference https://github.com/Microsoft/fsharplu/wiki/fsharplu.json is library by MSR.
It would be great to have this feature so DTO can be written in F# types. Currently…
17 votes -
pagination
Add support for pagination in queries with dynamodb.
Actually, when you set "limit" in Query or Scan methods, the first elements are obtained. This could be the first page. but there is no method that enables you obtain the second or third page.
Maybe, you can add a GetPage method, that returns a collection wrapper, inherited from Collection<T>. This wrapper could have the last evaluated key.
Then, GetPage method, could accept a query or scan expression, a page size and the last evaluated key
This could be very usefull for applications that needs paginate some results but don't need retrieve…
31 votes -
Parcelable in Android Studio auto-generated dtos
Can you make parcelable the auto-generated dtos by Android plugin for Android Studio?
1 vote -
Allow DateHandler to be specified at field level
It is currently possible to serialize dates as ISO8601DateOnly and ISO8601.
https://gist.github.com/georgehemmings/42d9841913d1da01e91b
The date handler applies to all DateTime fields in the object.
Where a DateTime field is representing only a date, it would be nice to emit this in ISO8601DateOnly but leaving any other DateTimes to emit in full ISO8601 format.
1 vote -
Improvements for batched requests
I've started working with request batching, which is a really nice feature. Everything works, but there two improvements I'd like to see.
Firstly, for IReturnVoid requests there is SendAllOneWay, but there is no async version of that method.
Secondly, I'd like to be able to specify a http Verb with the SendAll methods. The implementation should select the correct method in the service, both when calling a single request method multiple times, but also for the batched method. Right now the batched service methods always need to be Any(), it would be nice to be able to have Delete(OrderID[] orders).
3 votes -
Support Changing ViewPages directory
Support Allowing Custom ViewPages directory
Right now the convention of using a folder in root works great for the general case (We've been on service stack razor for at least a year). With that said we hit the point that we need to move the views into a subfolder to easier support a part of the subcontrol strategy.Would love to have the convention be default and a easy way to change the base folder for vies on the apphost configure method.
6 votes -
SDK Documentation
The c# SDK is seriously lagging in documentation. By that I mean IntelliSense documentation: it would be awsome with some "in line" documentation for methods and properties in the SDK
68 votes -
ServiceStack GraphQL endpoint
I've just stumbled upon Facebook's GraphQL and it's pretty slick.
The ability to query a ServiceStack endpoint using GraphQL would be a great addition (maybe similar to AutoQuery?) If ORMLite could also populate an object graph using a GraphQL query...51 votes -
OrmLite: Implicit Reference Conventions for string keys
I'm working with an existing legacy database schema. Many tables have string primary keys. These primary keys are typically named Code rather than Id. Id is reserved for int primary keys.
The implicit relationships are currently applied for properties ending in Id. It would be nice if this worked for properties ending in Code too (if marked with PrimaryKey attribute).
E.g.
q.Join<CustomerType>();
q.Join<CustomerType,Customer>((cust,type) => cust.CustomerTypeCode == type.Code);0 votes -
smal change in IndexOperationsControl.RenderRow
You could do a little modification to the IndexOperationsControl.RenderRow method, so that no row for an operation is rendered if no formats are available in the calling scenario.
Currently, if I protect an operation with
[Restrict(VisibilityTo = RequestAttributes.InternalNetworkAccess | RequestAttributes.AnyFormat)]
and i connect from an external network I see the operation with all formats disabled. It would be better not to see the operation at all.1 vote -
Provide an option in Save References to delete missing References
e.g:
db.Save(poco, references: true, deleteMissing: true);
from: https://forums.servicestack.net/t/ormlite-graph-update/1395
6 votes
- Don't see your idea?