-
The typescript types for `RelayEnvironementProvider` doesn't appear to be compatible with `@types/react@18.2.48`. React did some changes to how JSX element types are declared last year and recommended…
-
You should add `prop-types` because this library is `peerDependencies` of react-smooth https://github.com/recharts/react-smooth/blob/master/package.json#L44.
Otherwise a lot of warning will appear …
-
Recharts: "^1.7.1"
Warning:
```bash
Warning: Failed prop type: Line: prop type `points[0].value` is invalid; it must be a function, usually from the `prop-types` package, but received `undefined`…
-
This ticket is purely for the input components used for Props. The goal is to allow users to edit a selected component's props in the interface easily.
The prop types include:
- Code (esse…
-
Add react prop-types for the ``` ``` component.
-
## Context
In the upcoming React 19 `@types/` packages, [the props of `ReactElement` now default to `unknown` instead of `any`](https://github.com/DefinitelyTyped/DefinitelyTyped/pull/69022#:~:text…
-
Recently, a rule for `react/prop-types` was made a warning.
This issue is to investigate whether or not it is needed and to turn the rule off or to make it an error and fix the relevant code.
-
The user profile object stores `received_shares`, but the prop type is not configured properly based on the structure of how `received_shares` are stored. Update the prop types to match the structure.…
-
As `react` and `react-dom` are already defined as `devDependencies` i propose to to the same with `prop-types`.
Are there any cons?
eugef updated
5 years ago
-
Using `React.HTMLAttributes` as the prop type in a component definition causes false positives of `react/prop-types`.
Strangely enough, when adding indirection by extending that same type in an int…