WrappedComponent.defaultProps is missing in mapStateToProps

[wenbing]

class Foo extends React.Component {
  render() {
    return <div>this.props.bar</div>
  }
}

Foo.defaultProps = {
  bar: 'baz'
}

module.exports = connect(function mapStateToProps(state, props) {
  console.log(props.bar) // undefined 
})(Foo)

[gaearon]

connect() returns a new component. If you'd like defaultProps to be present on it, you need to put defaultProps on it:

class Foo extends React.Component {
  render() {
    return <div>this.props.bar</div>
  }
}

Foo = connect(function mapStateToProps(state, props) {
  console.log(props.bar) 
})(Foo)

Foo.defaultProps = {
  bar: 'baz'
}

module.exports = Foo;

[arcanis]

@gaearon shouldn't this be handled by the library? It doesn't feel very intuitive this way (especially when using decorators and static properties), and doing the opposite (by requiring to manually delete the defaultProps from the wrapper element should the forwarding be undesirable) seems a saner default behaviour.

[markerikson]

No, the current behavior makes sense based on both the tooling, the language syntax, and the conceptual idea of defining "original" components vs defining wrappers for them.