-
Notifications
You must be signed in to change notification settings - Fork 26
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Single nested enum fails due to no support in fleece #131
Comments
Discussed this here: fsprojects/Fleece#65 |
After discussion with @gusty we think this is best done in Fleece. |
@gusty Can you remember what needs to be done for this? |
Yes, there's no built-in support in Fleece for enums. We can add a default codec there, based either on numbers or names. We need to decide which, it sounds to me that names are best suited for human-readable json. Otherwise, since enums can't contain static members, the only way to encode them externally is by using explicit combinators. Let me know which way you would prefer to move forward, for Falanx. |
@gusty I think the reasoning around json encoding is to be more human readable so lets just go for names for now although the proto definition of json encoding is this:
|
OK, let's add an overload for this. |
This is done in Fleece. Once a new nuget is created we should be able to reference it and fix this. |
BTW: I think this
is also doable in Fleece, the question is whether it makes sense, as it would work one way only. |
Why closing this without merging #169 ? |
Just for the sake of closing it? But the issue is real and the PR that would solve it is not merged. |
I know, but in the OSS world you never know who's using what. If you're not the maintainer and can't merge the PR that will effectively close this issue, you should leave it open. By closing it this way you are giving the false information that the issue is resolved, when is not. |
Results in:
The text was updated successfully, but these errors were encountered: