-
Type:
Task
-
Resolution: Unresolved
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
-
3
-
None
-
Developer Tools
Our parser logic relies on methods being available on specific classes / interfaces from mongodb-java-driver. In the linked ticket, we even noticed that a small change in the API surface led to disruption in our parsing logic.
To avoid this situation in production, we should run nightly tests against the nightly builds of mongodb-java-driver, at-least the codeinsight tests. This should surface any parser related problems if the driver API surface changes and affects the parser.
- related to
-
INTELLIJ-183 Importing from mongodb-java-driver package in a Spring Criteria file messes up with dialect detection logic
-
- Backlog
-