You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
You can turn off the fp/no-mutation rule. Apart from that, no. Maybe if you give me some more information about your use-case, I could add options to the rule or create a new one, but I'm not sure that's wanted. Depends on your use-case really.
Sure! My use case is simple. I was using immutable.js, but serialization and deserialization suck, so I replaced it with plain objects and Ramda. Some people are using Object.freeze during development to prevent accidental object change. I think it's up to eslint to enforce such rule. The problem with current settings is, that people override variables a lot, but almost never mutate objects, because all these spread notations. What I need for https://github.com/este/este is the rule, which replaces these hacks https://github.com/rtfeldman/seamless-immutable#performance, but allow variable reassignment. Does it makes sense?
I can't enforce variables reassignment for actual project, but I can enforce it on object. It is possible to turn-off variables reassignment somehow?
The text was updated successfully, but these errors were encountered: