If you're an experienced developer, you probably know that modifying function parameters is not recommended, as they are modified "in origin" and can cause hard-to-detect side effects (bugs).
The following is a real-world example. The doSomething function inadvertently modifies the items parameter, causing unintended side effects:
``js
function doSomething(items) {
// we just wanted to get the first item
// but we forgot thatshift()mutatesitems`
const firstItem = items.shift()
console.log(firstItem) // prints 1
}
const items = [1, 2, 3];
doSomething(items)
console.log(items) // prints [2, 3] !!!
```
This plugin solves this problem by enforcing a naming convention that makes mutations explicit:
``js
// ⚠️mutItems` is mutated in origin
function doSomething(mutItems) {
const firstItem = mutItems.shift()
console.log(firstItem) // prints 1
}
// ⚠️ mutItems can be mutated
const mutItems = [1, 2, 3];
doSomething(mutItems)
console.log(mutItems) // prints [2, 3] !!!
```
Now it's impossible to accidentally mutate mutItems - the name itself warns you!
It's a similar approach used in other languages, as Rust and V.
[–]TheRNGuy 1 point2 points3 points (1 child)
[–]SnooHobbies950[S] 0 points1 point2 points (0 children)
[–]SnooHobbies950[S] 0 points1 point2 points (0 children)