Link together the check_* family

[DominiqueMakowski]

That is something we rarely use in the docstring, the "seealso" field. In that case, however, it could be useful to have all the check_* functions linked to one another, so that the user can discover and jump from function docs to function docs.

This could also be implemented via a paragraph in the details.

Aside from that, these functions are great and will necessitate a blogpost (and a vignette?) sooner or later ☺️

[strengejacke]

Aside from that, these functions are great and will necessitate a blogpost (and a vignette?) sooner or later

True, I wish I would have more time to write down at least a blog post... I think performance is a package of high usefuleness for many users, but doesn't have the popularity it probably deserve.

[DominiqueMakowski]

patience you must have. It'll come ☺️ I think after performance is out and report at least fixed, I'll try to write some posts :)

[strengejacke]

You mean parameters, not performance?

[DominiqueMakowski]

parameters* yup but it's ok as you read my mind 🔮

[IndrajeetPatil]

I think performance is a package of high usefuleness for many users, but doesn't have the popularity it probably deserve.

That aged poorly 😅

Yes, we can cross-link documentation files with @seealso and @family tags.

[IndrajeetPatil]

Thankfully, this is already the case of the pkgdown website, but I guess a number of users might be discovering functions via manual and help pages. The Rd tags will definitely be helpful for them to discover other checks.

[strengejacke]

How does @family work?

[mattansb]

I use it a lot in effectsize - https://github.com/easystats/effectsize/blob/main/R/cohens_d.R#L49

[strengejacke]

And what does it do in the docs?