Uploaded image for project: 'MongoDB for IntelliJ Plugin'
  1. MongoDB for IntelliJ Plugin
  2. INTELLIJ-81

Validation does not work for DB name/Collection name/field name in different cases

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 0.0.5
    • Affects Version/s: None
    • Component/s: None
    • Environment:
      OS:
      node.js / npm versions:
      Additional info:
    • Not Needed
    • Developer Tools

      Problem Statement/Rationale

      Following are different cases where DB, collection, and field name validation are not working.

      Case 1

      Validation works for field names in `find` but does not work for `getCollection()` or `getDatabase()`. I expect if I write a DB or collection that does not exist to also give me warning that my reference doesn't exist in the connected cluster. Video of case 1: https://drive.google.com/file/d/1NmvzUwkzF5xwTmsVvlLIxZCQzZKgrval/view?usp=sharing 

      Case 2

      When I write the query out fully and then go back and change field names, I don't get the same validation again for all the names: db/collection/field. I try closing, opening, and reassigning datastore to the file again and it still does not work. Video: https://drive.google.com/file/d/1RSPI6NphTi5XuBm2zCx1nai4WWUT4nuf/view?usp=sharing

      We might have to deal with each case separately if we think it is two different problems but putting them together as they seem related.

            Assignee:
            kevin.mas@mongodb.com Kevin Mas Ruiz
            Reporter:
            gaurab.aryal@mongodb.com Gaurab Aryal
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: