Router.go takes an unordered object, but arguments depends on ordering

[Karolusrex]

In Javascript, there is no guarantee of ordering of object properties. The ordering is crucial inside the controllers, so I would consider to make the arguments as an array.

[Karolusrex]

Essentially, it is not safe to pass more than one argument as I see it

[Karolusrex]

After reading a bit I saw that all browsers support ordering, although not explicitly supported by the specification. So this point might not be that urgent

[Karolusrex]

Solution with different syntax to solve this problem:

Instead of router.go(.., .., {param1: a, param2: b}), we can go for router.go(.., .., [['param1', a], ['param2', b]})

The router.go function can then create a new Map() of this last argument which is ordered by nature

[trbm1]

And maybe introducing a special parameter resolver to ensure correct formatting with the router. Like:
[['param1', a], ['param2', b]] = ParameterHelper.resolve({ param1: a, param2: b});

[trbm1]

Suggestion 2: using ES7 decorators. E.g.

@param.order('parm1', 'parm2')
    someControllerFunction(parm1, parm2) {
    }

and have either the query map to the specified order OR passing a simple JSON object to the router.go function. Making router.go as simple as:

router.go('someControllerFunction', 34,  'fff');

[tjclement]

I'm not too excited about the semantics of those solutions, but automatically parsing the correct argument order through reflection still seems super expensive: http://jsperf.com/function-tostring-performance.

Let's keep this parked for a little while longer.