Configuration: Add too_long_first_doc_paragraph lint to the check-private-items list

[bradjc]

I enabled the check-private-items configuration option and I found that the setting affects the too_long_first_doc_paragraph lint, however, that is not documented. I believe this change adds the connection between the lint and the configuration option so that it will show up in the docs.

The line became more than 120 characters so I believe I formatted it correctly on multiple lines, following the msrv example. Also, I preserved the alphabetical ordering.

changelog: [too_long_first_doc_paragraph]: add check-private-items as documented config option.

[rustbot]

Thanks for the pull request, and welcome!

You should hear from one of our reviewers after this PR gets at least 2 reviews from the community.

Please see the contribution instructions for more information. Namely, in order to ensure the minimum review times lag, PR authors and assigned reviewers should ensure that the review label (S-waiting-on-review and S-waiting-on-author) stays updated, invoking these commands when appropriate:

• @rustbot author: the review is finished, PR author should check the comments and take action accordingly
• @rustbot review: the author is ready for a review, this PR will be queued again in the reviewer's queue

[CommanderStorm]

community review: Yep, that is how it works. 👍🏻

To save others the search:

rust-clippy/clippy_lints/src/doc/too_long_first_doc_paragraph.rs

Lines 10 to 21 in 9117fa7

	use super::TOO_LONG_FIRST_DOC_PARAGRAPH;
	pub(super) fn check(
	cx: &LateContext<'_>,
	item: &Item<'_>,
	attrs: &[Attribute],
	first_paragraph_text_len: usize,
	mut first_paragraph_md_len: usize,
	check_private_items: bool,
	) {
	if !check_private_items && !cx.effective_visibilities.is_exported(item.owner_id.def_id) {
	return;

View changes since this review

[bradjc]

I just rebased after the recent conf reformat.

[rustbot]

This PR was rebased onto a different master commit. Here's a range-diff highlighting what actually changed.

Rebasing is a normal part of keeping PRs up to date, so no action is needed—this note is just to help reviewers.