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

Deserialization: no way to specify general key to property mapping #108

Closed
ghost opened this issue Oct 22, 2014 · 1 comment
Closed

Deserialization: no way to specify general key to property mapping #108

ghost opened this issue Oct 22, 2014 · 1 comment

Comments

@ghost
Copy link

ghost commented Oct 22, 2014

Deserialization would be easier if we could define and use general key to property mapping rules.
Basically like INamingConvention but in reverse way.

For example deserializing:

person:
    full name: Bob
    age: 15
    eats open-mouthed: yes

into

class Person
{
    public string FullName { get; set; }
    public int Age { get; set; }
    public bool EatsOpenMouthed { get; set; }
}

would be much easier if we could define and use general mapping like:

Key -> PascalCase

Currently one must FOR ALL properties either:

  1. use [YamlAlias]
  2. hardcode property name and use it in INamingConvention
@ghost ghost changed the title Deserialziation: no way to specify general key to property mapping Deserialization: no way to specify general key to property mapping Oct 22, 2014
@aaubry
Copy link
Owner

aaubry commented Sep 26, 2019

I'm sorry I was unable to answer this question in a timely fashion. As you have certainly moved on to other things, I will close this issue, but feel free to reopen it if necessary.

@aaubry aaubry closed this as completed Sep 26, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant