You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Code Quality] Fix ESLint no-core-exportvariable-non-string rule: extend alias coverage to coreObj #45864
The ESLint rule gh-aw-custom/no-core-exportvariable-non-string only matches callee.object.name === "core", making it blind to coreObj.exportVariable(...) calls. This diverges from the plugin's own CORE_ALIASES = {core, coreObj} convention used by sibling rules require-return-after-core-setfailed and require-await-core-summary-write.
Grounded blind call sites in actions/setup/js/parse_mcp_gateway_log.cjs:214 and :220 currently pass strings (.toFixed/String), so this is a coverage/consistency gap, not a live bug.
Suggested Changes
Update the rule implementation to match CORE_ALIASES (both core and coreObj)
Add test cases covering coreObj.exportVariable(nonString) to the rule's test suite
Files Affected
ESLint rule file for no-core-exportvariable-non-string (in actions/setup/js/ or eslint-plugin-gh-aw-custom/)
Corresponding rule test file
Success Criteria
Rule triggers on coreObj.exportVariable(nonString) the same as core.exportVariable(nonString)
Activity
github-actions commentedon Jul 17, 2026
This issue was automatically closed because it expired on 2026-07-17T01:21:07.541Z.