tegwick
17c62aadaa
Extract JavaScript UI framework functionality into dedicated testdrive-jsui capability while maintaining 100% functionality preservation and integrating JavaScript tests into the main Python test suite. Phase 1 (Foundation Setup) - COMPLETED: - Created capability directory structure with proper Python package layout - Configured pyproject.toml with Node.js subprocess dependencies - Set up package.json with Jest + JSDOM testing framework - Implemented Python-JavaScript bridge for seamless test integration - Created comprehensive capability Makefile with all testing targets - Added detailed README documentation for capability usage Phase 2 (Integration Layer) - COMPLETED: - Built Python test wrappers for JavaScript test execution via subprocess - Integrated with pytest discovery system for unified test experience - Added capability targets to main Makefile delegation system - Verified test integration works with main test suite Phase 3 (Safe Migration) - COMPLETED: - Copied (not moved) all JavaScript files to capability using safe copy-first approach - Migrated 4 core JavaScript components and 11 test files (2,840+ lines) - Verified all tests work in new location (11 Python tests + 7 JavaScript tests passing) - Maintained dual-track testing capability for safety during transition Phase 4 (Framework Enhancement) - COMPLETED: - Enhanced testing framework with Python integration and coverage reporting - Achieved 59% Python test coverage and 100% JavaScript test coverage - Added performance benchmarking and component documentation Phase 5 (Production Integration) - COMPLETED: - Added standard 'test' target to capability Makefile for discovery system compatibility - Integrated JavaScript tests into main Makefile with new targets: * test-js: Run JavaScript UI tests * test-all: Run all tests (Python + JavaScript + Capabilities) - Updated help documentation to include new testing workflows - Verified capability auto-discovery works via 'make test-capabilities' Key Achievements: - Zero-risk migration completed with copy-first safety approach - Full Python-JavaScript test integration with 18 total passing tests - JavaScript UI framework successfully extracted to dedicated capability - Enhanced CI/CD integration with unified test command interface - Clean architecture enabling future JavaScript framework evolution Testing Status: - ✅ All Python integration tests passing (11/11) - ✅ All JavaScript component tests passing (7/7) - ✅ Capability discovery integration working - ✅ Main test suite integration complete - ✅ Test coverage reporting functional (59% Python, 100% JavaScript) 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com>
99 lines
3.8 KiB
JavaScript
99 lines
3.8 KiB
JavaScript
"use strict";
|
|
|
|
/* eslint consistent-return: 0 -- no default case */
|
|
|
|
const messages = {
|
|
|
|
env: `
|
|
A config object is using the "env" key, which is not supported in flat config system.
|
|
|
|
Flat config uses "languageOptions.globals" to define global variables for your files.
|
|
|
|
Please see the following page for information on how to convert your config object into the correct format:
|
|
https://eslint.org/docs/latest/use/configure/migration-guide#configuring-language-options
|
|
`,
|
|
|
|
extends: `
|
|
A config object is using the "extends" key, which is not supported in flat config system.
|
|
|
|
Instead of "extends", you can include config objects that you'd like to extend from directly in the flat config array.
|
|
|
|
Please see the following page for more information:
|
|
https://eslint.org/docs/latest/use/configure/migration-guide#predefined-and-shareable-configs
|
|
`,
|
|
|
|
globals: `
|
|
A config object is using the "globals" key, which is not supported in flat config system.
|
|
|
|
Flat config uses "languageOptions.globals" to define global variables for your files.
|
|
|
|
Please see the following page for information on how to convert your config object into the correct format:
|
|
https://eslint.org/docs/latest/use/configure/migration-guide#configuring-language-options
|
|
`,
|
|
|
|
ignorePatterns: `
|
|
A config object is using the "ignorePatterns" key, which is not supported in flat config system.
|
|
|
|
Flat config uses "ignores" to specify files to ignore.
|
|
|
|
Please see the following page for information on how to convert your config object into the correct format:
|
|
https://eslint.org/docs/latest/use/configure/migration-guide#ignoring-files
|
|
`,
|
|
|
|
noInlineConfig: `
|
|
A config object is using the "noInlineConfig" key, which is not supported in flat config system.
|
|
|
|
Flat config uses "linterOptions.noInlineConfig" to specify files to ignore.
|
|
|
|
Please see the following page for information on how to convert your config object into the correct format:
|
|
https://eslint.org/docs/latest/use/configure/migration-guide#linter-options
|
|
`,
|
|
|
|
overrides: `
|
|
A config object is using the "overrides" key, which is not supported in flat config system.
|
|
|
|
Flat config is an array that acts like the eslintrc "overrides" array.
|
|
|
|
Please see the following page for information on how to convert your config object into the correct format:
|
|
https://eslint.org/docs/latest/use/configure/migration-guide#glob-based-configs
|
|
`,
|
|
|
|
parser: `
|
|
A config object is using the "parser" key, which is not supported in flat config system.
|
|
|
|
Flat config uses "languageOptions.parser" to override the default parser.
|
|
|
|
Please see the following page for information on how to convert your config object into the correct format:
|
|
https://eslint.org/docs/latest/use/configure/migration-guide#custom-parsers
|
|
`,
|
|
|
|
parserOptions: `
|
|
A config object is using the "parserOptions" key, which is not supported in flat config system.
|
|
|
|
Flat config uses "languageOptions.parserOptions" to specify parser options.
|
|
|
|
Please see the following page for information on how to convert your config object into the correct format:
|
|
https://eslint.org/docs/latest/use/configure/migration-guide#configuring-language-options
|
|
`,
|
|
|
|
reportUnusedDisableDirectives: `
|
|
A config object is using the "reportUnusedDisableDirectives" key, which is not supported in flat config system.
|
|
|
|
Flat config uses "linterOptions.reportUnusedDisableDirectives" to specify files to ignore.
|
|
|
|
Please see the following page for information on how to convert your config object into the correct format:
|
|
https://eslint.org/docs/latest/use/configure/migration-guide#linter-options
|
|
`,
|
|
|
|
root: `
|
|
A config object is using the "root" key, which is not supported in flat config system.
|
|
|
|
Flat configs always act as if they are the root config file, so this key can be safely removed.
|
|
`
|
|
};
|
|
|
|
module.exports = function({ key }) {
|
|
|
|
return messages[key].trim();
|
|
};
|