Skip to content

Feature Requests

← Customer Feedback for ServiceStack

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).

I suggest you ...

You've used all your votes and won't be able to post a new idea, but you can still search and comment on existing ideas.

There are two ways to get more votes:

  • When an admin closes an idea you've voted on, you'll get your votes back from that idea.
  • You can remove your votes from an open idea you support.
  • To see ideas you have already voted on, select the "My feedback" filter and select "My open ideas".
(thinking…)

Enter your idea and we'll search to see if someone has already suggested it.

If a similar idea already exists, you can support and comment on it.

If it doesn't exist, you can post your idea so others can support it.

Enter your idea and we'll search to see if someone has already suggested it.

162 results found

  1. 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
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    0 comments  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

  2. Add MQ Fallback on Service Clients for one-way requests

    If a remote remote HTTP Service is unavailable add optional fallback functionality to an MQ endpoint for automated resilience/recovery.

    0 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    0 comments  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
1 2 … 5 6 7 9 Next →
  • Don't see your idea?

Feature Requests

Categories

Feedback and Knowledge Base

(thinking…)