Uploaded image for project: 'C# Driver'
  1. C# Driver
  2. CSHARP-5572

Implement new version of the KnownSerializerFinder

XMLWordPrintableJSON

    • Type: Icon: Improvement Improvement
    • Resolution: Unresolved
    • Priority: Icon: Critical - P2 Critical - P2
    • None
    • Affects Version/s: None
    • Component/s: LINQ
    • None
    • None
    • Dotnet Drivers
    • 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

      In CSHARP-5375 we removed the KnownSerializerFinder thinking that it was no longer needed.

      We have since discovered a few scenarios that actually can only be solved with something similar to the KnownSerializerFinder we removed.

      We had good reasons to remove the KnownSerializerFinder, so I don't think we should simply bring it back as it was.

      What would probably work well is a new version of the KnownSerializerFinder that actually infers which serializer to use at various nodes in the expression tree starting from nodes for which the serializer is known. This is different from the original KnownSerializerFinder which just relied on which serializers it had "seen", but didn't apply any rules as to where that serializer might then be appropriately used.

            Assignee:
            robert@mongodb.com Robert Stam
            Reporter:
            robert@mongodb.com Robert Stam
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: