[SERVER-32650] Filter part of Compass contains false and confusing definition of itself. Created: 10/Jan/18  Updated: 27/Oct/23  Resolved: 18/Jan/18

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: 3.4.10
Fix Version/s: None

Type: Bug Priority: Trivial - P5
Reporter: Ismayil Aliyev Assignee: Sam Weaver
Resolution: Works as Designed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: PNG File bug_mongodb1.png    
Operating System: ALL
Steps To Reproduce:

1. Install MongoDB Compass for instance 3.4.10 version
2. Establish connection to Database
3. Click on "Filter" tab
4. Check placeholder

Participants:

 Description   

Currently the filter part of MongoDB Compass has wrong definition.
In order to filter anything we need to pass key and value of items in collections.

Received result is:

{field:'value'}

Expected result is following:

{key:'value'}

It is confusing and could be misinterpreted.



 Comments   
Comment by Sam Weaver [ 18/Jan/18 ]

Hi there,

Thanks for the submission. Typically we refer to key-value pairings as "fields" and values. For example, our documentation talks about fields, and we try to remain consistent with it's usage: https://docs.mongodb.com/manual/reference/method/db.collection.find/#projection

I appreciate your concern/confusion around the vernacular but "field" is our preferred team here.

Best regards,
Sam

Comment by Ismayil Aliyev [ 16/Jan/18 ]

Hello,

Could you please clarify the status of bug?

Thank you!

Generated at Thu Feb 08 04:30:52 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.