-
Type:
Task
-
Resolution: Unresolved
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
-
8
-
Iteration B (May 5 - May 16), Iteration C (May 19 - May 30), Iteration D (June 2 - June 13)
-
Not Needed
-
Developer Tools
- is related to
-
INTELLIJ-342 findOneAndReplace in java-driver gets generated as findOneAndDelete in mongosh query
-
- Needs Triage
-
-
INTELLIJ-343 Should not catch ProcessCancelledException
-
- Needs Triage
-
-
INTELLIJ-344 Invalid version error still popping up in stack traces
-
- Needs Triage
-
-
INTELLIJ-345 Annotator failed for MongoDBCollectionDoesNotExist inspection
-
- Needs Triage
-
-
INTELLIJ-346 Insight filtering failed because of virtualFile being null when accessed
-
- Needs Triage
-
- related to
-
INTELLIJ-336 Spring Criteria query with .and("field").is(invalid_type) does not trigger a linter warning
-
- Closed
-
-
INTELLIJ-337 Linters doesn't seem to be triggered in aggregations with Spring Criteria when it has a limit
-
- Closed
-
-
INTELLIJ-333 Sorting should not complain on hybrid int | double fields
-
- Closed
-
-
INTELLIJ-334 In Spring Criteria, Sort.by(Direction, String...) has an invalid linter warning
-
- Closed
-
-
INTELLIJ-335 Spring Criteria does not autocomplete when the query is in a variable, but linters work
-
- Closed
-
-
INTELLIJ-338 Spring Criteria aggregate with project.andExclude is considered a Dynamic Query
-
- Closed
-
-
INTELLIJ-340 Spring Criteria, when generating a query with a dynamic namespace, the namespace selector of the run query dialog does not load databases and collections
-
- Closed
-