Property names for dynamic types are not deserialized with PascalCasing

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Won't Fix
    • Priority: Minor - P4
    • None
    • Affects Version/s: 2.0
    • Component/s: Serialization
    • None
    • None
    • Hide

      1. What would you like to communicate to the user about this feature?
      2. Would you like the user to see examples of the syntax and/or executable code and its output?
      3. Which versions of the driver/connector does this apply to?

      Show
      1. What would you like to communicate to the user about this feature? 2. Would you like the user to see examples of the syntax and/or executable code and its output? 3. Which versions of the driver/connector does this apply to?
    • None
    • None
    • None
    • None
    • None
    • None

      Serialization with default settings keeps the original property name casing, Pascal in particular. Using camelCasing convention works properly, and ensures the camel casing fields in the DB.

      Unfortunately the deserialization leaves the names in the camel casing making the data incompatible with the domain that expects PascalCasing in the code.

      The goal is to have camelCasing in the DB and PascalCasing in the code.

      Serialization/Deserialization process should be compatible with each other.

            Assignee:
            Unassigned
            Reporter:
            Lenny Granovsky
            Votes:
            1 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: