Audit naming conventions in extensions optimizations

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • Query Integration
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Running List of Naming Suggestions to Consider/Apply:

      • [alyssa.clark@mongodb.com] I wonder if we should name `evaluate_rule_precondition` something like evaluate_pipeline_rewrite_rule_*? I'm just wondering if it is confusing without more context in the name since it isn't associated with any classes that indicate the context
      • Use better param names than "out" for bool out param on api functions?

            Assignee:
            Unassigned
            Reporter:
            Adithi Raghavan
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: