My feedback

  1. 17 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Feature Requests  ·  Flag idea as inappropriate…  ·  Admin →
    Brent supported this idea  · 
    An error occurred while saving the comment
    Brent commented  · 

    Regarding option types, we can get half-way there by registering custom serializers. See:

    (Just remember to register the serializers before initializing your AppHost)

    One problem is that generated DTO binding files will expose the property as a custom type called FSharpOption<T>. This might be okay for a F# client (although I haven't tested it), but it's inconvenient for other clients like C#. We've basically pushed the "semantic mismatch" from the server to the client.

    A second problem is that even if ServiceStack.Text recognized supported Option<T> similar to the Nullable<T> type, what is supposed to happen when we have a non-option CLR reference type property on your DTO, like string? This could be null over the wire, and would somehow need to be validated to ensure it is not-null.

    It's an interesting problem!

Feedback and Knowledge Base