eslint-plugin-react-native icon indicating copy to clipboard operation
eslint-plugin-react-native copied to clipboard

React Native plugin for ESLint

Results 91 eslint-plugin-react-native issues
Sort by recently updated
recently updated
newest added

Hi there, I am probably doing something wrong, if not a lot of things, but I can't figure out what. I have Googled, and I have read through the issues...

We using destructuring on your StyleSheet.create object you get a "Unused style detected" warning, even though the style is in use. Example: ``` //This gives no warning const styles =...

Would it be possible to have some rule that StyleSheet.create-variables can be used before defined? If I understand correctly that is the best practice and that collides with `no-use-before-define`

Here is example component where `no-unused-styles` works: ![image](https://user-images.githubusercontent.com/12229968/64013223-04baeb80-cb28-11e9-85d8-fc3f7c8cf1c4.png) But if the same component is refactored to functional component the validation is not working anymore ![image](https://user-images.githubusercontent.com/12229968/64013279-1e5c3300-cb28-11e9-8fd6-f6606799d43d.png) Also the docs https://github.com/Intellicode/eslint-plugin-react-native/blob/master/docs/rules/no-unused-styles.md don't...

help wanted

Hello, Thank you for creating and maintaining these rules, they are very useful! I think I found an issue with how the `no-inline-styles` rule determines to warn you about usage...

As per title, when using ``, eslint does not report any errors. However, `` does work ```jsx import React from 'react'; import { View, StyleSheet } from 'react-native'; export default...

I don't expect `no-raw-text` to fail in this case according to [the tests](https://github.com/Intellicode/eslint-plugin-react-native/blob/master/tests/lib/rules/no-raw-text.js#L53-L65), but it does for me. ```js import React from "react"; import { View, Text } from "react-native";...

bug

Right now `split-platform-components` has false-positives if file extension is different than `js`, i.e. `jsx` or `tsx`. This rule should be either extension-agnostic or at least allow providing option (regex?) so...

documentation

One of the things I notice myself doing a lot during development is moving inline styles out after I finalize them. I thought it could increase my and hopefully others'...

Example: ``` import React, { memo } from 'react'; import { Text, StyleSheet } from 'react-native'; const styles = StyleSheet.create({ container: { padding: 1, }, critical: { backgroundColor: 'red', },...