zap-api-nodejs methods should allow for passing argument Objects

Is your feature request related to a problem? Please describe.

Presently, the arguments to API calls are positional as shown in the script.load function.

This presents a usability issue since you end up needing to pass null for optional arguments.

Additionally, the arguments are immediately converted into a params variable.

Describe the solution you’d like

I would like to be able to pass all options as an Object which would be used as params and/or merged with the defaults if there are any.

Describe alternatives you’ve considered

None.

Screenshots

No response

Additional context

I noted that the comments indicated that the code was auto-generated so I wasn’t going to start working on any PRs until I had a grasp of that mechanism if it is still in use.

Would you like to help fix this issue?

• Yes

[thc202]

how can they be integrated to Java code

There’s not much to integrate the generator just needs to output the corresponding text. It worth noting that not all parameters are documented and the actual type is not available (they will always be string right now).

[trevor-vaughan]

@njmulsqb I’m currently using it to drive the ZAP API automatically from a node.js CLI.

Being able to drive things in Node allows me to easily port it over to a web view at some point if I want to.

If you’re building web apps, you’re probably already doing some level of front end building with Node so adding yet another language (Python) is unnecessary.