You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have types that must target multiple versions of a target JSON format, and I am wondering if I can use Fleece without being forced to drop down to using combinators to manually wire things together.
Lets say I have the following:
typeName= Name ofParts:stringlistmemberToJson(options:MorphirJsonFormatOptions)= failwith "TODO: encode using options"andMorphirJsonFormatOptions=| Classic ofVersion:int| NextGen ofNextGenVersionOptionsandNextGenVersionOptions={Version:Version ; NameEncodingMode:NameEncodingMode}andVersion= Version ofMajor:int*Minor:int*Patch:intandNameEncodingMode=| ArrayStyle
| SnakeCasedSymbol
Are there any recommendations how I can still benefit from the SRTP resolution?
The text was updated successfully, but these errors were encountered:
I think this question is quite interesting. The question about how an API should be able to decode/encode different versions with a sort of ambient context such as options that you want to thread into the codecs.
I have types that must target multiple versions of a target JSON format, and I am wondering if I can use Fleece without being forced to drop down to using combinators to manually wire things together.
Lets say I have the following:
Are there any recommendations how I can still benefit from the SRTP resolution?
The text was updated successfully, but these errors were encountered: