Skip to content

Conversation

@aruntyagiTutu
Copy link
Contributor

@aruntyagiTutu aruntyagiTutu commented Jan 7, 2026

part1 - Modularize ESLint rule mappings and related refactors

Changes (by area)
ESLint engine
Split RULE_MAPPINGS into per-plugin modules; aggregate in src/rule-mappings.ts.
Added shared tag constants in src/rule-mappings/constants.ts.
[Add other changes here as you commit them, e.g., config tweaks, docs, tests, etc.]

No behavioral changes expected; only file-structure refactor for rule mappings.
Risk and compatibility
Low risk; RULE_MAPPINGS export path and shape unchanged.
Consumers importing ./rule-mappings remain unaffected.

part2 - updated tests and added relevent tests

part3 - Added two entries to .vscode/launch.json:
Debug engine.test.ts (single test): runs a targeted Jest test in-band, no coverage.
Debug Jest (watch all): watch mode for all tests in-band, no coverage.
Uses NODE_OPTIONS=--experimental-vm-modules and integrated terminal.
Non-breaking; existing configs retained.

Demo: https://salesforce-internal.slack.com/archives/G02JGHG9NSE/p1767964298744989

@aruntyagiTutu aruntyagiTutu changed the title @W-20773626@ - ESLint rules for react typescript static analysis [WIP] [Do not comment] New @W-20773626@ ESLint rules for react typescript static analysis Jan 8, 2026
@aruntyagiTutu aruntyagiTutu changed the title New @W-20773626@ ESLint rules for react typescript static analysis NEW @W-20773626@ ESLint rules for react typescript static analysis Jan 8, 2026
Copy link
Contributor

@namrata111f namrata111f left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

1- Let's test for the existing Typescript code as well to verify no regression for it. The Typescript violations should continue to be reported as expected.
2- React Team has shared one good repo with .tsx file for testing: https://github.com/salesforce-experience-platform-emu/vibe-coding-starter/tree/main/static-app/src/components. We can verify if the violations reported on these files are valid.

@aruntyagiTutu aruntyagiTutu merged commit c2f5bcd into dev Jan 12, 2026
7 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants