From 03e53e3964908d77068ed7d8538a046222b56d55 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Timoth=C3=A9e=20Mazzucotelli?= Date: Tue, 9 Jan 2024 15:56:45 +0100 Subject: [PATCH] docs: Tell that members are still grouped by category when specifying members or members order options Issue #119: https://github.com/mkdocstrings/python/issues/119 --- docs/usage/configuration/members.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/docs/usage/configuration/members.md b/docs/usage/configuration/members.md index 0b6d27e5..f558040f 100644 --- a/docs/usage/configuration/members.md +++ b/docs/usage/configuration/members.md @@ -14,6 +14,8 @@ even if [`show_if_no_docstring`][] is set to false. The members will be rendered in the specified order, regardless of the value of [`members_order`][]. +**Note that members will still be grouped by category, +according to the [`group_by_category`][] option.** Passing a falsy value (`no`, `false` in YAML) or an empty list (`[]`) will tell the Python handler not to render any member. @@ -269,6 +271,8 @@ The members ordering to use. Possible values: The order applies for all members, recursively. The order will be ignored for members that are explicitely sorted using the [`members`][] option. +**Note that members will still be grouped by category, +according to the [`group_by_category`][] option.** ```yaml title="in mkdocs.yml (global configuration)" plugins: