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>
48 lines
2.2 KiB
Markdown
48 lines
2.2 KiB
Markdown
# eslint-plugin-es-x
|
|
|
|
[](https://www.npmjs.com/package/eslint-plugin-es-x)
|
|
[](http://www.npmtrends.com/eslint-plugin-es-x)
|
|
[](https://github.com/eslint-community/eslint-plugin-es-x/actions)
|
|
|
|
ESLint plugin which disallows each ECMAScript syntax.
|
|
|
|
> Forked from [eslint-plugin-es](https://github.com/mysticatea/eslint-plugin-es). As the original repository seems [no longer maintained](https://github.com/mysticatea/eslint-plugin-es/issues/72).
|
|
|
|
## 🏁 Goal
|
|
|
|
[Espree](https://github.com/eslint/espree#readme), the default parser of [ESLint](https://eslint.org/), has supported `ecmaVersion` option.
|
|
However, the error messages of new syntax are not readable (e.g., "unexpected token" or something like).
|
|
|
|
When we use this plugin along with the latest `ecmaVersion` option value, it tells us the readable error message for the new syntax, such as "ES2020 BigInt is forbidden."
|
|
Plus, this plugin lets us disable each syntactic feature individually.
|
|
|
|
## 📖 Usage
|
|
|
|
See [documentation](https://eslint-community.github.io/eslint-plugin-es-x/)
|
|
|
|
## 🚥 Semantic Versioning Policy
|
|
|
|
This plugin follows [semantic versioning](http://semver.org/) and [ESLint's semantic versioning policy](https://github.com/eslint/eslint#semantic-versioning-policy).
|
|
|
|
- We will release a new minor version to add new rules when TC39 decided to advance proposals to Stage 4. In the minor releases, we don't update configs.
|
|
- We will release a new major version to update configs when new ECMAScript snapshots are available.
|
|
|
|
## 📰 Changelog
|
|
|
|
See [releases](https://github.com/eslint-community/eslint-plugin-es-x/releases).
|
|
|
|
## ❤️ Contributing
|
|
|
|
Welcome contributing!
|
|
|
|
Please use GitHub's Issues/PRs.
|
|
|
|
### Development Tools
|
|
|
|
- `npm test` runs tests and measures coverage.
|
|
- `npm run clean` removes the coverage result of `npm test` command.
|
|
- `npm run coverage` shows the coverage result of the last `npm test` command.
|
|
- `npm run docs:build` builds documentation.
|
|
- `npm run docs:watch` builds documentation on each file change.
|
|
- `npm run watch` runs tests on each file change.
|