-
Type:
Bug
-
Resolution: Unresolved
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
-
Environment:OS: Windows 11 Pro
Compass version: 1.53.0
MongoDB: Atlas cluster
node.js / npm versions: N/A (Compass desktop app)
-
None
-
None
-
Developer Tools
In the Documents tab (JSON view), some documents show a large nested field
(a GeoJSON MultiPolygon) fully expanded when the results load, even though
I never expanded it. The field cannot be collapsed: there is no fold arrow
next to the key, so it takes hundreds of lines on screen.
Other documents in the same collection, with the exact same structure, show
the same field collapsed ({…}) as expected.
The behavior does not seem to depend on depth or size:
- Both fields have identical structure:
{ type: "MultiPolygon", coordinates: [[[[lng, lat], ...]]] } - In the same document, a larger field (`geometry`, ~178 KB) renders collapsed,
while a smaller field (`geometrySimplified`, ~91 KB) renders expanded and
cannot be collapsed.
Steps to reproduce
1. Collection with documents containing two GeoJSON MultiPolygon fields
(`geometry` and `geometrySimplified`), tens to hundreds of KB each,
some with dozens of polygons (islands).
2. Open the collection in Compass, Documents tab, JSON view.
3. Run Find with an empty filter.
Expected
All nested objects/arrays render collapsed ({…} / […]) and every one of them
can be expanded/collapsed with its fold arrow.
Actual
In some documents the `geometrySimplified` field renders fully expanded on load
and has no fold arrow, so it cannot be collapsed. The `geometry` field in the
same document renders collapsed correctly.
Workaround
Use a projection ({ geometry: 0, geometrySimplified: 0 }) or the List/Table view.
Screenshot attached: first document (collapsed as expected) vs. second document
(`geometrySimplified` expanded, not collapsible).