JS-937 Support grpc in Node process

[vdiez]

No description provided.

[vdiez]

Note on rule parameter type parsing in gRPC vs HTTP bridge

The parseParamValue function in transformers.ts handles type conversion from strings, which may seem redundant if you're familiar with the HTTP bridge workflow. Here's why it's needed:

HTTP Bridge (existing analyze-project workflow)

• Java's configurations() method returns typed objects: Map.of("max", 7) where 7 is an int
• Gson serializes to JSON with proper types: {"max": 7}
• Node receives already-typed values via JSON parsing

gRPC (new workflow)

• Proto3 sends rule params as string key-value pairs: [{key: "maximumFunctionParameters", value: "7"}]
• The transformer must parse "7" → 7 based on the field's default type from config.ts

This is by design - the gRPC endpoint receives raw @RuleProperty string values, while the HTTP bridge receives the output of the Java configurations() method which already contains properly typed values.

[vdiez]

Summary of rule options transformation work

What was implemented

The gRPC endpoint now properly transforms rule parameters from SonarQube format to ESLint format:

1. Key mapping: SonarQube param keys (e.g., maximumFunctionParameters) are mapped to ESLint field names (e.g., max) using the displayName ↔ field mapping from config.ts

2. Type parsing: String values from proto3 are parsed to proper types based on the field's default value:

   • "5" → 5 (number)
   • "true" → true (boolean)
   • "a,b,c" → ["a", "b", "c"] (string array)
   • "1,2,3" → [1, 2, 3] (number array)

3. Language filtering: Rules are only created for languages they support (from languages in generated-meta.ts)

4. Scope handling: fileTypeTargets is set based on rule scope - ['TEST'] for test-only rules, ['MAIN', 'TEST'] for main rules

5. Unknown rules/params: Gracefully skipped without errors

Other changes

• Removed findCommonBaseDir: Since canAccessFileSystem: false, the baseDir is irrelevant - simplified to '/'
• Refactored esbuild: Common build logic extracted to esbuild-common.mjs
• Documentation: Added comprehensive "Rule Options Architecture" section to docs/DEV.md explaining how fields, schema, defaultOptions, and Java @RuleProperty all fit together

Test coverage

12 unit tests in packages/grpc/tests/transformers.test.ts covering:

• Key mapping with displayName
• Numeric/boolean/string/array param parsing
• Language filtering (JS-only, TS-only, both)
• Scope-based fileTypeTargets
• Unknown rules and params handling

[sonarqube-next]

Quality Gate passed

Issues
0 New issues
1 Accepted issue

Measures
0 Security Hotspots
0 Dependency risks
82.7% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube