4👍
If I am going straight to answer your question I can tell you that eslint is using this rule to warn you about an unintended side effect. As per the eslint-plugin-vue docs
It is considered a very bad practice to introduce side effects inside computed properties. It makes the code not predictable and hard to understand.
Basically what we need to remember is that computed properties are meant to be used when there’s heavy logic associated to how we treat data inside templates. So you shouldn’t be updating any properties/data inside a computed property logic.
I would like to help you further if you provide a more detailed example of what you’re trying yo achieve
👤Taro
Source:stackexchange.com