Static methods are fundamentally different from instance methods, in that they do not work on the instance itself. Since there is a semantic difference, it would make sense to list them separately in the sidebar, listing "Static Methods" before "Methods".
Static methods can also be used as factory methods, which makes showing them separated from instance methods even more sensible (creating an object is the first step in working with them) - constructors are listed separately too, after all.
I'd love to have a config option "separateStaticMethods" or something similar, which would stop mixing static methods into regular ones, listing them before instance methods both in the body of the page as well as the sidebar.
One could further argue that static methods should even be listed before properties (meaning just after constructors), because both properties and instance methods are relevant to the instance, while static methods are on more of a "meta" level.
However, I would not list them before constructors, as constructors tie into the definition of a class itself, and are thus arguably the "most important" part.
All of this is incredibly subjective, obviously.
But I'd like to have that option.
Static methods are fundamentally different from instance methods, in that they do not work on the instance itself. Since there is a semantic difference, it would make sense to list them separately in the sidebar, listing "Static Methods" before "Methods".
Static methods can also be used as factory methods, which makes showing them separated from instance methods even more sensible (creating an object is the first step in working with them) - constructors are listed separately too, after all.
I'd love to have a config option "separateStaticMethods" or something similar, which would stop mixing static methods into regular ones, listing them before instance methods both in the body of the page as well as the sidebar.
One could further argue that static methods should even be listed before properties (meaning just after constructors), because both properties and instance methods are relevant to the instance, while static methods are on more of a "meta" level.
However, I would not list them before constructors, as constructors tie into the definition of a class itself, and are thus arguably the "most important" part.
All of this is incredibly subjective, obviously.
But I'd like to have that option.