use field path prefix consistently on rhs expressions

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Done
    • Priority: Major - P3
    • 2.1.0
    • Affects Version/s: None
    • Component/s: Aggregation Framework
    • None
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      I've gotten complaints from people after two of the sneak peek talks I've done about being inconsistent about the use of $ at the beginning of field paths on the right hand side of projection and other specifications. There are contexts where it is not required, because the fact that the specification is a field path is unambiguous, and this has made people unsure of where and when they are required. I'll make it consistent.

              Assignee:
              Chris Westin (Inactive)
              Reporter:
              Chris Westin (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: