unknown props warning

current.js

const ContactBadge = (props) => (
  <div className='Badge' {...props}>
    <div>{props.user.name}</div>
    <div>{props.contactMethod.type}</div>
  </div>
);

export default connect((state, {userId, contactMethodId}) => ({
  user: selectUser(state, userId),
  contactMethod: selectContactMethod(state, contactMethodId)
}))(ContactBadge);

delete.js

//Using clone+delete to satisfy unknown props warning
const ContactBadge = (props) => {
  const divProps = {...props};
  delete divProps.user;
  delete divProps.contactMethod;
  delete divProps.userId;
  delete divProps.contactMethodId;
  delete divProps.dispatch;
  
  return (
    <div className='Badge' {...divProps}>
      <div>{props.user.name}</div>
      <div>{props.contactMethod.type}</div>
    </div>
  );
};

export default connect((state, {userId, contactMethodId}) => ({
  user: selectUser(state, userId),
  contactMethod: selectContactMethod(state, contactMethodId)
}))(ContactBadge);

destructure.js

//Using destructuring to satisfy unknown props warning
const ContactBadge = ({user, contactMethod, userId, contactMethodId, dispatch, ...rest}) => (
  <div className='Badge' {...rest}>
    <div>{user.name}</div>
    <div>{contactMethod.type}</div>
  </div>
);

export default connect((state, {userId, contactMethodId}) => ({
  user: selectUser(state, userId),
  contactMethod: selectContactMethod(state, contactMethodId)
}))(ContactBadge);

@burakcan This is not a solution we recommend. Those modules are internal and may be changed/removed in any release.

@gaearon, yes we're aware of that. But in that case, there's only one file to change.