咨询：redux-form中FieldArray修改props是否违反函数式编程原则

Great question—this is a super common point of confusion when first working with redux-form's FieldArray component, so let's unpack it clearly.

First, let's recap the key functional programming principles that matter here:

• Immutability: Data shouldn't be modified in-place; instead, new copies are created whenever state changes.
• Pure components: Components should avoid direct side effects, and their output should depend only on their input props.

Now, let's break down what's actually happening in that example. When you call methods like this.props.fields.push() or this.props.fields.remove(index), you're not directly mutating the props passed to your component. Those methods are special wrappers from redux-form that dispatch Redux actions under the hood.

Here's the real flow:

1. The fields prop is a set of helper functions tied to your Redux store's form state.
2. When you call push(), it sends an action to the Redux reducer. The reducer then creates a new copy of the field array (keeping immutability intact) instead of altering the original data.
3. Once the store updates, your component gets fresh props via Redux's connect HOC, triggering a re-render with the updated field list.

This is the critical distinction: you're not modifying the props themselves—you're using props as a clean interface to trigger controlled state changes in the centralized store. This aligns perfectly with functional programming principles because:

• Your component stays a pure function of its props; it never modifies data directly.
• All state updates are handled immutably in the reducer.
• Side effects (like updating form state) are isolated to Redux's predictable action/reducer flow.

In fact, this pattern is intentional in redux-form. It leverages Redux's unidirectional data flow to keep dynamic form state predictable and easy to debug. The "modification" you're seeing is just a user-friendly API for interacting with the store, not a violation of functional programming rules.

To sum it up: this isn't an anti-pattern—it's a standard, idiomatic way to handle dynamic form fields in the Redux ecosystem that respects core functional programming ideas.

内容的提问来源于stack exchange，提问作者jbojcic