[prop-types] add elementType and resetWarningCache

[eps1lon]

Please fill in this template.

• Use a meaningful title for the pull request. Include the name of the package modified.
• Test the change in your own code. (Compile and run.)
• Add or edit tests to reflect the change. (Run with npm test.)
• Follow the advice from the readme.
• Avoid common mistakes.
• Run npm run lint package-name (or tsc if no tslint.json is present).

If changing an existing definition:

• Provide a URL to documentation or source code which provides context for the suggested changes:
  • 15.7 changelog
  • PropTypes.resetWarningCache() added with Export resetWarningCache facebook/prop-types#178
  • PropTypes.elementType (right under optionalElement) added with Add a PropTypes for React elementType (ie. MyComponent) facebook/prop-types#211
• Increase the version number in the header if appropriate.
• If you are making substantial changes, consider adding a tslint.json containing { "extends": "dtslint/dt.json" }.

[eps1lon]

I did look into the react-jss since I'm familiar with the package and the fail looked like it was related: Don't think it actually is. Error occurred on master to and was fixable with

diff --git a/types/react-jss/react-jss-tests.tsx b/types/react-jss/react-jss-tests.tsx
index 5fe76ae1..cfcad4cd 100644
--- a/types/react-jss/react-jss-tests.tsx
+++ b/types/react-jss/react-jss-tests.tsx
@@ -27,9 +27,9 @@ interface ButtonProps {
   active?: boolean;
 }
 
-const styles = (theme: MyTheme) => createStyles({
+const styles = (theme: MyTheme) => createStyles<ButtonProps>({
   myButton: {
-    color: (props: ButtonProps) => props.active ? 'red' : theme.color.primary,
+    color: props => props.active ? 'red' : theme.color.primary,
     margin: 1,
     "& span": {
       fontWeight: "revert"

[typescript-bot]

@eps1lon Thank you for submitting this PR!

🔔 @DovydasNavickas @ferdaber - please review this PR in the next few days. Be sure to explicitly select Approve or Request Changes in the GitHub UI so I know what's going on.

If no reviewer appears after a week, a DefinitelyTyped maintainer will review the PR instead.

[typescript-bot]

@eps1lon The Travis CI build failed! Please review the logs for more information.

Once you've pushed the fixes, the build will automatically re-run. Thanks!

[ferdaber]

Can you add a test for the exotic components like React.Fragment and React.lazy()?

[eps1lon]

Can you add a test for the exotic components like React.Fragment and React.lazy()?

@ferdaber How would this look like? As far as I know I can't expect a specific type in the typescript interface and then validate a less specific type in propTypes. In this case I can't declare component?: LazyExoticComponent in the interface and the use component: elementType.

[ferdaber]

I meant a test that those components, when passed in as props, passes the JSX.LibraryManagedAttributes check. I should clarify: I was talking about React types tests not PropTypes types tests 😅

They're tightly coupled so changes to this package almost necessarily needs a retest of the library-managed-attributes.ts test file in @types/react.

[eps1lon]

@ferdaber the managedAttributes.tsx tests are completely commented out though. I really have no idea what tests I should add.

[ferdaber]

I don't want this change to be blocked because of tests so I'll go ahead and approve.

[typescript-bot]

A definition owner has approved this PR ⭐️. A maintainer will merge this PR shortly. If it shouldn't be merged yet, please leave a comment saying so and we'll wait. Thank you for your contribution to DefinitelyTyped!

[typescript-bot]

I just published @types/prop-types@15.7.0 to npm.