How getcouped/eslint-plugin-react-google-translate works
This small ESLint plugin flags JSX text-node patterns that may break with Google Translate and React components that return text directly. A developer enables the plugin in ESLint; ESLint applies its rules to code and reports findings. The recommended configuration activates both rules. Relationships reflect the README and excerpts; no other runtime subsystems are present.
Main entry points: index.js Plugin Entry · no-conditional-text-nodes-with-siblings.js Conditional Text Rule · no-return-text-nodes.js Return Text Rule
Components 6
Other components
- Developer
- ESLint
- Plugin Entry
lib/index.js - Conditional Text Rule
lib/rules/no-conditional-text-nodes-with-siblings.js - Return Text Rule
lib/rules/no-return-text-nodes.js - Lint Findings
Connections 8
- Developer → Plugin Entry: configures
README.md - ESLint → Plugin Entry: loads
README.md - Plugin Entry → Conditional Text Rule: registers
lib/index.js - Plugin Entry → Return Text Rule: registers
lib/index.js - ESLint → Conditional Text Rule: applies
README.md - ESLint → Return Text Rule: applies
README.md - Conditional Text Rule → Lint Findings: reports
lib/rules/no-conditional-text-nodes-with-siblings.js - Return Text Rule → Lint Findings: reports
lib/rules/no-return-text-nodes.js