**Do you want to request a _feature_ or report a _bug_?**
Enhancement

**What is the current behavior?**
Element type checker is not as informative as the other ones.

**What is the expected behavior?**
It would be nice to provide the actual type of the prop passed similarly to other type checkers. I.e., instead of 

> Invalid prop `Prop` supplied to `Component`, expected a single ReactElement.

say

> Invalid prop `Prop` of type `type` supplied to `Component`, expected a single ReactElement.

**Which versions of React, and which browser / OS are affected by this issue? Did this work in previous versions of React?**
Seeing this on 15.2.1 but I think it's also applicable to previous versions.

I know the general intention is to move away from prop types, but if there isn't a specific reason for the current behavior I can look into making this more pretty.

{'0': 'maybe-array', length: 1}
      );
      expectWarningInDevelopment(PropTypes.arrayOf(PropTypes.number).isRequired, null);
      expectWarningInDevelopment(PropTypes.arrayOf(PropTypes.number).isRequired, undefined);
    });
  });
  describe('Component Type', function() {
    beforeEach(function() {
      Component = React.createClass({
        propTypes: {
          label: PropTypes.element.isRequired,
        },
        render: function() {
          return <div>{this.props.label}</div>;
        },
      });
    });
    it('should support components', () => {
      typeCheckPass(PropTypes.element, <div />);
    });
    it('should not support multiple components or scalar values', () => {
      var message = 'Invalid prop `testProp` supplied to `testComponent`, ' +
        'expected a single ReactElement.';
      typeCheckFail(PropTypes.element, [<div />, <div />], message);
      typeCheckFail(PropTypes.element, 123, message);
      typeCheckFail(PropTypes.element, 'foo', message);
      typeCheckFail(PropTypes.element, false, message);
    });
    it('should be able to define a single child as label', () => {
      spyOn(console, 'error');