.NET Analyzer stops working after failed analysis

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: Unknown
    • 1.4.0
    • Affects Version/s: None
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      The .NET Analyzer does not show the 3 dots to analyze expressions for builders once it fails on an analysis of Builders

      var builder = Builders<Restaurant>.Filter;
      var filter = builder.Eq(r => r.Name, "Mongo Pizza");

      The 2nd line above causes expressions as shown below to fail analysis

      var filter = Builders<Restaurant>.Filter.Eq(r => r.Name, name1) |
          Builders<Restaurant>.Filter.Eq(r => r.Name, name2);
      Restaurant result = _restaurantsCollection.Find(filter).FirstOrDefault();

      This example uses the Sample Restaurant dataset from MongoDB Atlas. 

      Acceptance Criteria: 

      • The Analyzer should gracefully continue to analyze other expressions even if it fails on one. 

              Assignee:
              Ravi Raghavan (Inactive)
              Reporter:
              Rishit Bhatia
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: