Visually highlight the warning about using $min xor $max #2221
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Following up from DOCS-4015, the second paragraph in the "$min without $max" and "$max within $min" sections should be more noticable, since it is warning the user of hazardous usage that is best avoided.
|
edited and merged |
mongo-cr-bot
pushed a commit
that referenced
this pull request
Dec 2, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Following up from DOCS-4015, the second paragraph in the "$min without $max" and "$max within $min" sections should be more noticable, since it is warning the user of hazardous usage that is best avoided.
If it's not appropriate to have such a warning box inside a "fact" file (rather than a "warning" file), then it should be easy enough to rearrange as necessary.