What's the deal with the @params in JavaScript

The @params in js

simply it's documentation for function parameters.

benefits

code completion in equipped editors

description of parameters and types to the consumers of the function "API" - especially for a JavaScript module

what it is not:

a type enforcer e.g the typescript compiler, if a function is expecting a string and you pass a number it yells at you, the @param does not do that; u have to handle that by your self as you see in the image i handled errors or unwanted types with typeof: Screenshot (838)

How does it work(simply)

step 1 : you must have a function with parameters that can be documented

here is our pokeBall function with three paramters

function PokeBall(name, abilities, cb){

    if(typeof name === "string" && typeof abilities === "object" && typeof cb === "function"){
        let theChosenOne = `You chose ${name} ability : ${abilities.name} power: ${abilities.power}`

        cb(theChosenOne, null)
    }
    else {
      cb(null, `incorrect params`)
    }



}

2 document "usually" on top of the func
- first the comments thingy s /***/

/**
*
* @callback cb_
* @param {Object}  val - returned val from the database
* @param {String}  err - returned error from the database
*
*/

a simple form or shape of the documentation (JSDoc) is:

e.g : @param {String} myString - this is my string

Going over the examples

documenting PokeBall params

/**
 *
 * @param {String} name - name of the pokemon
 * @param {Object} abilities -   pokemon abilities
 * @param {String} abilities.name -   ability name
 * @param {Number} abilities.power  pokemon name
 *
 * @param {cb_} cb - callback function
 *
 */