While Vue does allow for props mutation, it is generally not recommended. According to the documentation found at https://vuejs.org/guide/components/props.html#one-way-data-flow, it is advised to avoid mutating nested props unless there is a tight coupling between the parent and child components.
Although this approach may seem acceptable, various forum posts strongly advise against it due to potential issues such as data corruption upon re-rendering of the parent component (Vue 2 - Mutating props vue-warn).
Personally, I prefer to follow the recommendations rather than engaging in debates regarding this practice. However, the team I am part of heavily relies on prop mutation.
While it currently works for us, I have concerns about potential problems that may arise in the future. Are there any risks of Vue prohibiting prop mutation in upcoming versions or making subtle changes that are only compatible with one-way data flow?
I am curious how others handle situations where deep object changes are necessary. Implementing these changes using emits requires numerous adjustments across all components in between.
Additionally, I am interested to know how common the practice of prop mutation is among developers. Is anyone else following the same approach?