EventLogging uses JSDuck, which can't process the DocBlocks in the JS Client Library

It looks like JSDuck is configured to exclude the files in modules/lib. I wasn't able to test this locally (Ruby issues), but as a short term solution, you could try including those files and using @inheritdoc.

Update EventLogging to use JSDoc

This is definitely something that should happen at some point as part of the project to migrate off of JSDuck (T138401), but there will be some work needed to update the tags to work with JSDoc. I did a quick test locally, and it looks like JSDoc's @borrows would fix the issue here. Let me know when you're interested in starting the process to migrate to JSDoc, and I can open a patch to get it started.

@apaskulin We are interested now! Thank you very much for your help!

Great! I've opened T357444: Migrate EventLogging to JSDoc. I can open a WIP patch to get it started by the end of the week, but feel free to claim the task and start sooner if you'd like.

I've opened a patch for T357444: Migrate EventLogging to JSDoc, just need someone familiar with the extension (and particularly the MetricsClient) to do the review. To run the docs locally, see the instructions at https://gerrit.wikimedia.org/g/jsdoc/wmf-theme#local-development

This was done by @apaskulin as part of the patch for T357444: Migrate EventLogging to JSDoc.

The DocBlock for mw.eventLog.submit() is visible and borrowed from MetricsClient#submit() and the same is true for mw.eventLog.dispatch(). The latter is also correctly marked as deprecated.