-
Notifications
You must be signed in to change notification settings - Fork 25k
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
Fix deprecation in history retention docs #53655
Fix deprecation in history retention docs #53655
Conversation
This commit adjusts a `deprecation[...]` message in the docs since such messages must be on a single line. It also moves this message to the start of the description of the deprecated setting as is the case with other such messages.
Pinging @elastic/es-docs (>docs) |
Pinging @elastic/es-distributed (:Distributed/Engine) |
Ugh, preview at http://elasticsearch_53655.docs-preview.app.elstc.co/guide/en/elasticsearch/reference/master/index-modules-history-retention.html indicates this is still wrong, but I've no idea why. I guessed c07e3c0. |
Ok, latest preview looks good. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM.
Just as a note: This also changes the deprecation notice from a block (using ::
) to inline (using :
). I think that's appropriate here tho. Here are the deprecation tag docs if that helps next time:
https://github.com/elastic/docs#additions-and-deprecations
Re: 2761b2d, the So change:
To:
This is sort of the reason why we're moving away from the Thanks for pointing out the inconsistency in those docs. I'll get that fixed. |
This commit adjusts a `deprecation[...]` message in the docs since such messages must be on a single line. It also moves this message to the start of the description of the deprecated setting as is the case with other such messages.
This commit adjusts a `deprecation[...]` message in the docs since such messages must be on a single line. It also moves this message to the start of the description of the deprecated setting as is the case with other such messages.
LGTM2. Thanks David. |
This commit adjusts a
deprecation[...]
message in the docs since suchmessages must be on a single line. It also moves this message to the start of
the description of the deprecated setting as is the case with other such
messages.