Sean
My feedback
3 results found
-
2 votes
An error occurred while saving the comment Sean supported this idea ·
-
163 votes
Please send any feedback to kaylee.won@mongodb.com going forward – this feature is under review, so we would love to hear from you. Thanks!
Sean supported this idea ·
-
14 votes
Sean shared this idea ·
An error occurred while saving the comment Sean commented
Touching a collection on the left hand side, wipes out your work in aggregations with no warning
When using aggregations and you are busy with your pipeline(s)
If you left click on any of the collections on the left panel,
It wipes out your work on the aggregations (no warnings at all)
[Yet when we paste in an exported version of the pipeline it gives a warning]
This makes it hard to teach people how to use aggregations, as they have to treat the left hand panel like a land mine (and all they wanted to do was to look up the name for the field)
Proposed fixes:
give a warning you are about to erase your work
- this would be bad for new user journey, they wouldn't know why the warning was there
don't erase and just open in a new tab
- this would create more tabs openAn error occurred while saving the comment Sean commented
Touching a collection on the left hand side, wipes out your work in aggregations with no warning
When using aggregations and you are busy with your pipeline(s)
If you left click on any of the collections on the left panel,
It wipes out your work on the aggregations (no warnings at all)
[Yet when we paste in an exported version of the pipeline it gives a warning]
This makes it hard to teach people how to use aggregations, as they have to treat the left hand panel like a land mine (and all they wanted to do was to look up the name for the field)
Proposed fixes:
give a warning you are about to erase your work
- this would be bad for new user journey, they wouldn't know why the warning was there
don't erase and just open in a new tab
- this would create more tabs open
Adding comment here
Example usage,
On live you have authentication, via a public address
But on pre-live env security says you may not expose the address to public ever.
This prevents pre-live environments from matching Live env
AND making it complex to work around not having URL address via VPC