The method names of the class are sorted to a point, then it starts over again. (unless this is intended behavior).
You can see in this example, it is sorted up until whereCondition and then starts in a sorted order from dateToMs

My jsdoc.json
{
"source": {
"include": [
"SQL"
],
"includePattern": ".js$",
"excludePattern": "(node_modules/|docs)"
},
"plugins": [
"./node_modules/jsdoc/plugins/markdown"
],
"templates": {
"cleverLinks": true,
"monospaceLinks": true
},
"opts": {
"recurse": true,
"destination": "./docs/",
"template": "./node_modules/docdash"
},
"docdash": {
"sort": [
true
]
}
}
UPDATE
I see that the STATIC methods are grouped after the non-static methods. I guess this must be the expected behaviour, but it was not initially obvious to me.
The method names of the class are sorted to a point, then it starts over again. (unless this is intended behavior).
You can see in this example, it is sorted up until whereCondition and then starts in a sorted order from dateToMs
My jsdoc.json
{ "source": { "include": [ "SQL" ], "includePattern": ".js$", "excludePattern": "(node_modules/|docs)" }, "plugins": [ "./node_modules/jsdoc/plugins/markdown" ], "templates": { "cleverLinks": true, "monospaceLinks": true }, "opts": { "recurse": true, "destination": "./docs/", "template": "./node_modules/docdash" }, "docdash": { "sort": [ true ] } }UPDATE
I see that the STATIC methods are grouped after the non-static methods. I guess this must be the expected behaviour, but it was not initially obvious to me.