Question: Is the team open to JS-Doc tags being added for better IDE experience.

Describe the bug or issue here…
Not a bug, but a question. I'm a big fan of the team's attitude towards Typescript ;) - I feel like what you guys do here with pure JS is a great example of what's possible.

However, there are some genuinely great developer experience / onboarding benefits to having JS Doc tags for function params / responses, especially considering you guys have already implemented proper models for all your domain entities.

It basically gives you all the DevEx things people rave about TypeScript, with none of the "tax", because it's all just vanilla JS.

I'd be curious about doing some of the tagging myself as a way of learning how the editor works in-detail, but I obviously don't want to waste my time if it's something the team isn't interested in having in the project.

The proposal concerns JSDoc tags for function parameters and responses in the JavaScript editor, especially the existing domain entity models. First confirm whether the team wants this direction and determine the scope of functions to annotate. Done would mean an agreed annotation plan, but the issue does not identify files or tests to use.

Written by the indexing model from the issue text.