rusackas opened a new pull request, #35354:
URL: https://github.com/apache/superset/pull/35354

   ## Summary
   
   This PR flattens the ESLint configuration by extracting all rules from 
`eslint-config-airbnb` directly into our `.eslintrc.js` file and removing the 
Airbnb dependency. This gives us full control over our linting rules and 
modernizes our configuration.
   
   ### Changes Made
   
   1. **Extracted all Airbnb rules**: Added 426 rules (251 core ESLint + 175 
plugin rules) directly to our configuration
   2. **Removed Airbnb dependency**: Removed `eslint-config-airbnb` from 
package.json
   3. **Added required plugins to config**: Added `import`, `jsx-a11y`, and 
`react-hooks` to the plugins array (these were already installed as 
dependencies)
   4. **Cleaned up redundant rules**: Removed 116 redundant rules that were 
either:
      - Set to ESLint defaults (62 rules)
      - Deprecated (6 rules)
      - Already at their default values (48 rules)
   
   ### Benefits
   
   - **Full control**: All ESLint rules are now explicitly in our config
   - **Transparency**: No hidden rules from external configs
   - **Maintainability**: Easier to understand and modify our linting setup
   - **Modern approach**: Aligns with ESLint's direction toward flat configs
   - **No new dependencies**: All required plugins were already installed
   
   ### Testing
   
   - ✅ All existing ESLint rules continue to work
   - ✅ `npm run lint` passes without any new violations
   - ✅ No changes to actual code, only configuration
   
   🤖 Generated with [Claude Code](https://claude.ai/code)


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to