Avoid unnecessary use of FieldPath inside ExpressionObject

XMLWordPrintableJSON

    • Fully Compatible
    • Query 2016-11-21
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      Inside ExpressionObject::evaluateInternal() we use MutableDocument::setNestedField() and a FieldPath, perhaps to handle dotted paths? But when parsing we assert the field names do not contain dots. We should use MutableDocument::addField() and stick with the string for both performance and clarity.

            Assignee:
            Charlie Swanson
            Reporter:
            Charlie Swanson
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: