It is recommended to always add propTypes for a component as it avoids runtime errors. Using propTypes ensures valid properties being passed as props or being used as props.
Occurrences
There is 1 occurrence of this issue in the repository.
The default behavior of any HTML button element is to perform a form submit when the type attribute is not present. To avoid unexpected behavior such as accidental page reloads, always provide a value for the type attribute on button elements.
Occurrences
There is 1 occurrence of this issue in the repository.
The issue is raised because of missing or unescaped JSX escape characters. These characters would be injected as a text node in JSX statements, which might not be intentional. These won't throw any syntax or runtime errors, but the rendered output will not be the same as expected.
Occurrences
There are 3 occurrences of this issue in the repository.
Components without children can be self-closed to avoid the unnecessary extra closing tag. In JSX, closing tags are required when the component has children example <MyComponent>...</MyComponent> and if there are no child component between these tags, then this component can be self closed using <MyComponent />. It is recommended as …
Occurrences
There are 4 occurrences of this issue in the repository.
It is recommended to use PascalCase for user-defined React JSX components since it uses the upper vs. lower case convention to distinguish between local component classes and HTML tags.
Occurrences
There are 8 occurrences of this issue in the repository.
The issue is raised because of missing or unescaped JSX escape characters. These characters would be injected as a text node in JSX statements, which might not be intentional. These won't throw any syntax or runtime errors, but the rendered output will not be the same as expected.
Occurrences
There are 3 occurrences of this issue in the repository.
The issue is raised because of missing or unescaped JSX escape characters. These characters would be injected as a text node in JSX statements, which might not be intentional. These won't throw any syntax or runtime errors, but the rendered output will not be the same as expected.
Occurrences
There are 3 occurrences of this issue in the repository.
It is recommended to have comments just before or immediately at the start of a function or class declaration/expression so that anyone who reads the code understands the purpose of the particular function or class.
Occurrences
There are 16 occurrences of this issue in the repository.
It is recommended to always add propTypes for a component as it avoids runtime errors. Using propTypes ensures valid properties being passed as props or being used as props.
Occurrences
There is 1 occurrence of this issue in the repository.
Variable that are not defined but they are being used in the code. This would give a potential errors that may break the code. It might have happen due to mistype of the variable name.
Occurrences
There is 1 occurrence of this issue in the repository.