Skip to content

DOCSP-48522-update-mongosh-history-log-description #394

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Conversation

amalhotra-mdb
Copy link
Contributor

@amalhotra-mdb amalhotra-mdb commented Mar 19, 2025

DESCRIPTION

Update mongosh history log descriptions.

STAGING

JIRA

https://jira.mongodb.org/browse/DOCSP-48522

BUILD LOG

Self-Review Checklist

  • Is this free of any warnings or errors in the RST?
  • Is this free of spelling errors?
  • Is this free of grammatical errors?
  • Is this free of staging / rendering issues?
  • Are all the links working?

External Review Requirements

What's expected of an external reviewer?

Copy link

netlify bot commented Mar 19, 2025

Deploy Preview for docs-mongodb-shell ready!

Name Link
🔨 Latest commit 40ce350
🔍 Latest deploy log https://app.netlify.com/sites/docs-mongodb-shell/deploys/67e2bd4a2bf5620008cab1ff
😎 Deploy Preview https://deploy-preview-394--docs-mongodb-shell.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

Copy link

@feliciahsiehdb feliciahsiehdb left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm

Copy link
Collaborator

@ajhuh-mdb ajhuh-mdb left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for picking this up @amalhotra-mdb! Just a couple small comments.

@@ -103,12 +103,16 @@
* - ``redactHistory``
- string
- ``remove``
- Controls what information is recorded in the shell history.
- Controls what information is recorded in the ``mongosh`` command history,
meaning what can be accessed via up and down keys and Ctrl+R while inside the shell.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

[suggestion] Instead of using a dependent clause here, I think we can just split this up into separate sentences to make it more concise/simple. Maybe something like:

Controls what information is recorded in the `mongosh` command history. You can access the `mongosh` command history via the up and down...

- Controls what information is recorded in the shell history.
- Controls what information is recorded in the ``mongosh`` command history,
meaning what can be accessed via up and down keys and Ctrl+R while inside the shell.

Must be one of:
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

[suggestion] I know you didn't make this change, but it might be clearer if this introductory text doesn't end with a preposition

Suggested change
Must be one of:
Must be one of the following values:

Copy link
Collaborator

@ajhuh-mdb ajhuh-mdb left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm with one small nit!

Must be one of:
- Controls what information is recorded in the ``mongosh`` command history.
You can access the ``mongosh`` command history via the up and down keys
and Ctrl+R while inside the shell.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

[question/nit] Should we say "or" here since the Ctrl + R search mechanism in mongosh is separate from the up & down key navigation of the command history?

Suggested change
and Ctrl+R while inside the shell.
or Ctrl+R while inside the shell.

@amalhotra-mdb amalhotra-mdb merged commit 60d56b4 into mongodb:master Mar 25, 2025
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants