Add support for different encodings for unions about fsharp.systemtextjson HOT 6 CLOSED

I think the best would be to do what you propose by default (ie Some stored as just the value; None is already stored as null), with an opt-out flag for people who need to distinguish between None and Some null (or Some None).

from fsharp.systemtextjson.

I would propose adding another option called BareFieldlessTags This will encode cases without any fields as just the case name. For example:

• ExternalTag ||| BareFieldlessTags:

{ "Foo": [ 123, "hello" ] }

"Bar"

• ExternalTag ||| NamedFields ||| BareFieldlessTags:

{ "Foo": { "x": 123, "y": "hello" } }

"Bar"

The motivation is when serializing Unions that represent a series of simple codes.

from fsharp.systemtextjson.

That's a great idea!

from fsharp.systemtextjson.

That's great to have a choice. But I don't need it for Options. its a special case from my sight. Should be just serialized to value inside of Some and None to null

from fsharp.systemtextjson.

Agree, though that's their fault if they model option of option or list of option, etc. :)

from fsharp.systemtextjson.

Closing as this was released in v0.4 (the union issue is handled in #16).

from fsharp.systemtextjson.