Why assignment to property of function parameter is bad style.

[zhaoxiongfei]

Node.js web service

(req, res, next) => {
  req.user = Guest;
  return next();
};

Often used, can not be avoided.
How should I do?

[ljharb]

Since express does require this, you currently can only disable the rule entirely, on a per-file basis, or on a per-line/per-function basis.

eslint has an option proposed to cover this: eslint/eslint#6505

Once that's enabled, we'll likely enable it by default to cover req, request, and $scope.

[zhaoxiongfei]

Thank you sir.

[ljharb]

(the question's answered, but reopening to track the eslint rule change)

[felixsanz]

@zhangchitc You are not reassigning the parameter, you are just creating a property on the object.

Because of this, you can allow it today with "no-param-reassign": ["error", { "props": false }],.

[ljharb]

Yes, but "props": true is something that should be strictly enforced everywhere, except where a framework requires it, like express. The eslint rule change would be for "props": true, but with exceptions for req, etc.

[christianbundy]

Just a quick update, this has been merged and will be released in the next version of ESLint (which I believe is tomorrow): eslint/eslint#6505 (comment)

[shanev]

Another example is ctx in Koa routing:

router.get('/', (ctx) => {
  ctx.status = 200;
});

[ljharb]

The next release of eslint-config-airbnb-base, and likely eslint-config-airbnb, will include this loosening of no-param-reassign.

[jbruni]

no-param-reassign as "never reassign parameters" is ok.

no-param-reassign as "never mutate parameters" means eslint-config-airbnb enforces immutability paradigm. It makes a profound design choice for us.

[ljharb]

@jbruni Airbnb's config makes many profound design choices for you; that's the point. If you don't agree with them, you can easily override rules and/or fork the guide.

[kholiavko-roman]

Guys does anybody knows how to set up eslit for showing error if I modify value from param array ?
Here is example:

const checkIsValid = (id, array) => {
  for (let i = 0; i < array.length; i++) {
    const item = array[i];

    if (item.param) {
      item.value = null;
      item.payment = null;
    }
  }

  return array;
};

[ljharb]

@kholiavko-roman that’s pushing the limits of static analysis; you may want to try eslint-plugin-immutable, but it’s not very reliable due to the way the language works.

[aboyton]

@kholiavko-roman Or try TypeScript and something like jonaskello/tslint-immutable.

[kholiavko-roman]

Thanks for reply. I think I will try eslint-plugin-immutable for the first.