My parameters get reordered in the documentation

[SofiK]

Hi I have an issue,
I have a method with inputParameters like follows: (originalValues: MyRecord, newRecord: any, fieldNames: string[], fields: string[])

and in the documentation the parameters get reordered to
(originalValues: MyRecord, fieldNames: Array, fields: Array, newRecord: any)

Why does the newRecord parameter appear last? Is it because it is of type any? Cause at the moment it has to be. And I want it to be the second parameter. How can I fix that?

According to npm list -g I have TypeDoc 0.1.2.

I hope you can help me, Thank you in advance.

[SofiK]

I just noticed that this issue have already been reported and fixed: #39
Can I update to a working solution using npm?

[sebastian-lenz]

Hi SofiK, thank you for your report. As you already have noticed, the bug you've encountered looks like a duplicate of #39. The bug affects the ordering of parameters of function signatures and arrow functions.

The fix is already in the repro but not on NPM. Meanwhile you can download the fixed binary and copy it over to your installation. When installed locally the binary is usually located in node_modules/typedoc/bin, when installed globally you should be able to find the location by running which typedoc.

[SofiK]

Hi,
And thank you for the response.

I have typedoc installed globally. I couldn't write which, but where worked and I got the following location C:\Users\myuser\AppData\Roaming\npm\typedoc And I found the bin folder where the typedoc.js file is located. I removed it and added the one from https://raw.githubusercontent.com/sebastian-lenz/typedoc/master/bin/typedoc.js
But when I recreated the documentation, I still had the same issue. Do I have to do something else as well? Or is this another issue?

A more complete definition of my method is:
public static createUpdateRecord(originalValues: MyRecord, newRecord: any, fieldNames: string[], mandatoryFields: string[]): MyRecord {

[SofiK]

I tried testing to move around the parameters and changing types, when the newRecord and fieldNames switch places, it's the fieldNames that end up last. It always seems to be the second parameter that is moved to the end.

[SofiK]

I have tested some more and it depends on the code within the method. When I comment out part of the code, the variable goes back to the second position.
I cannot explain this but I had two for loops within the method, and when I Changed the second of them to a Array.foreach instead the documentation is generated correctly.

Here I have created a stupid test method which for me makes the parameters jump around (with newRecord last). It's really stupid, with unused variables and so.. :
public static caTest(originalValues: MIRecord, newRecord: any, fieldNames: string[], mandatoryFields: string[]): string {

        var returnval = "";
        var updates: string[] = [];
        var allFields: string[] = fieldNames;
        for (var j = 0; j < allFields.length; j++) {
            var field = allFields[j];
            var oldValue = originalValues[field];
            var newValue = newRecord[field];
        }
        return returnval;
    }

Can you see if this stupid method creates the issue for you too?
Thank you again for all help.

[sebastian-lenz]

Thank you very much for your efforts. I've included your demo in my test cases and could find the bug that caused the sorting of parameters. I've just released a new version on NPM, you should be able to get the latest code with npm update -g.

[SofiK]

Thank you!