Skip to content
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

Road map of features #119

Closed
15 of 18 tasks
neuecc opened this issue Aug 31, 2017 · 9 comments
Closed
15 of 18 tasks

Road map of features #119

neuecc opened this issue Aug 31, 2017 · 9 comments

Comments

@neuecc
Copy link
Member

neuecc commented Aug 31, 2017

MessagePack for C# aims to be ultimate serializer for .NET.
Ultimate means fastest and has full featured.

Road map of features.

@alexvaluyskiy
Copy link

alexvaluyskiy commented Aug 31, 2017

Some feature requests:

@crocuis
Copy link

crocuis commented Sep 1, 2017

Some feature requests :

  • v1.7.0. property custom serialize like Json.net
public class Organisation {
  public string Name { get; set; }
  [JsonConverter(typeof(TycoonConverter))]
  public IPerson Owner { get; set; }
}
  • Automatic generation of IntKey
[MessagePackObect(Order: ...)]
public class Organisation {
}

@francescocristallo
Copy link

francescocristallo commented Sep 4, 2017

Some feature Request:

  • camelCase Option

  • NullValueHandling = NullValueHandling.Ignore Option (as in Json.net), to avoid serializing null values

@alexvaluyskiy
Copy link

NullValueHandling.Ignore

@neuecc Is it make sense for MessagePack?

@neuecc
Copy link
Member Author

neuecc commented Sep 5, 2017

@alexvaluyskiy In string key mode, it is valid. MsgPack Serializer in other languages will also work well.

@hiradyazdan
Copy link

hiradyazdan commented Aug 29, 2019

@neuecc How about in int key mode for raw byte arrays? Can null values be automatically removed beforehand?

@hiradyazdan
Copy link

hiradyazdan commented Sep 17, 2019

I think it would also make sense if null values are skipped/ignored in int key mode as well where there are multiple schemas for the same type that have different properties (e.g. on different environments than c#). Two possible solution would be either to;

  • create multiple classes to contain different properties and keys
  • create a custom formatter that handle eliminating/adding extra properties

However, both these solutions require manual manipulation every time there's a change. This would be more cumbersome specially on AOT that needs pre-code generation. However, I was thinking of letting the generator to have an option to either skip or allow null values based on user's requirement or even allow both to create multiple formatters.

@AArnott
Copy link
Collaborator

AArnott commented Sep 19, 2019

@hiradyazdan This issue is for tracking accepted and planned feature work. Can you please open a separate issue if you wish to continue your suggestion?

@github-actions
Copy link
Contributor

github-actions bot commented Apr 2, 2020

This issue is stale because it has been open 90 days with no activity. Remove stale label or comment or this will be closed in 5 days.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

6 participants