Schema-aware autocomplete
Completions come from your collections, and they follow fields through the stages that reshape them.
Checked against v1.11.0 Updated
- Field path suggestions with type annotations (String, Number, ObjectId, Date) derived from schema analysis
- Progressive nested field disclosure shows only the current nesting level
- Pipeline-accumulated fields. $addFields, $group, $project, and $lookup output feeds autocomplete in later stages
- Reshaping stages replace the field list, removal stages filter out dropped fields, and disabled stages are skipped
- $lookup resolves the foreign collection’s schema for nested paths like customer.address.city
- Every MongoDB query and update operator, and the collection and cursor methods, with inline documentation
- Every aggregation stage, accumulator and expression operator, up to the MongoDB 8.x surface
- Stage-aware string completions. $lookup.from suggests collections, $unwind suggests array fields, $group._id suggests field references
- $facet branches expose sub-pipeline output, and $unionWith merges the other collection’s schema
- Enum value suggestions inside $in, $nin, $eq, $ne, and direct field comparisons
- Type-aware operators: $regex for strings, $gt/$lt for numbers and dates, $size/$elemMatch for arrays
- $expr context switching. Inside $expr in $match, autocomplete moves to aggregation expressions
- System variables ($$ROOT, $$NOW, $$REMOVE) and variables from $let, $map, $filter, and $reduce, in scope only
- BSON constructors with snippet placeholders: ObjectId(), NumberLong(), NumberDecimal(), UUID(), BinData(), Timestamp()
- $jsonSchema keyword suggestions inside validator expressions
- Suggestions are advisory. They never block execution, and stale schema data degrades them without breaking MongoDB language completions
- Index-aware ranking is an aggregation builder feature. The main editor does not have it