Prefer single objects for method & callback parameters over multiple arguments

[azy-1]

For many of the functions exposed by the API that accept more than two parameters, it would be more beneficial to instead pass an object where the arguments are keyed.

This would eliminate any concern about the order of the arguments passed in, provide API stability by preventing the addition / removal of method parameters from breaking existing code, and greatly improve overall code readability and extensibility - especially so in the case of functions where several of its parameters share the same type.

Example 1

Current - multiple args (far less readable at a glance, order of args is crucial):

Instance.DebugScreenText("Hello, world", 16, 16, 3, { r: 255, g: 0, b: 0 });

Proposed - single object (immediately clear what each value represents, extensible, order of args is irrevelant):

Instance.DebugScreenText({
  text: "Hello, world",
  x: 16,
  y: 16,
  duration: 3,
  color: { r: 255, g: 0, b: 0 },
})

Example 2

This proposal also extends to methods that accept a callback as a parameter, where it would be more useful if those callbacks were instead passed an object, as this would allow you to destructure that object and access specific properties, rather than needing to leave unused parameters, e.g:

Current:

Instance.OnPlayerChat((speaker, team, text) => {
  Instance.Msg(text)
})

Proposed:

Instance.OnPlayerChat(({ text }) => {
  Instance.Msg(text)
})

Example where this is already implemented:

OnScriptInput(name: string, callback: (inputData: { caller?: Entity; activator?: Entity }) => void): void;

[Poggicek]

Added in https://steamcommunity.com/games/CSGO/announcements/detail/498333631688738078