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>
152 lines
4.4 KiB
Markdown
152 lines
4.4 KiB
Markdown
### Version 4.0.0 (2018-01-28) ###
|
||
|
||
- Added: Support for ES2018. The only change needed was recognizing the `s`
|
||
regex flag.
|
||
- Changed: _All_ tokens returned by the `matchToToken` function now have a
|
||
`closed` property. It is set to `undefined` for the tokens where “closed”
|
||
doesn’t make sense. This means that all tokens objects have the same shape,
|
||
which might improve performance.
|
||
|
||
These are the breaking changes:
|
||
|
||
- `'/a/s'.match(jsTokens)` no longer returns `['/', 'a', '/', 's']`, but
|
||
`['/a/s']`. (There are of course other variations of this.)
|
||
- Code that rely on some token objects not having the `closed` property could
|
||
now behave differently.
|
||
|
||
|
||
### Version 3.0.2 (2017-06-28) ###
|
||
|
||
- No code changes. Just updates to the readme.
|
||
|
||
|
||
### Version 3.0.1 (2017-01-30) ###
|
||
|
||
- Fixed: ES2015 unicode escapes with more than 6 hex digits are now matched
|
||
correctly.
|
||
|
||
|
||
### Version 3.0.0 (2017-01-11) ###
|
||
|
||
This release contains one breaking change, that should [improve performance in
|
||
V8][v8-perf]:
|
||
|
||
> So how can you, as a JavaScript developer, ensure that your RegExps are fast?
|
||
> If you are not interested in hooking into RegExp internals, make sure that
|
||
> neither the RegExp instance, nor its prototype is modified in order to get the
|
||
> best performance:
|
||
>
|
||
> ```js
|
||
> var re = /./g;
|
||
> re.exec(''); // Fast path.
|
||
> re.new_property = 'slow';
|
||
> ```
|
||
|
||
This module used to export a single regex, with `.matchToToken` bolted
|
||
on, just like in the above example. This release changes the exports of
|
||
the module to avoid this issue.
|
||
|
||
Before:
|
||
|
||
```js
|
||
import jsTokens from "js-tokens"
|
||
// or:
|
||
var jsTokens = require("js-tokens")
|
||
var matchToToken = jsTokens.matchToToken
|
||
```
|
||
|
||
After:
|
||
|
||
```js
|
||
import jsTokens, {matchToToken} from "js-tokens"
|
||
// or:
|
||
var jsTokens = require("js-tokens").default
|
||
var matchToToken = require("js-tokens").matchToToken
|
||
```
|
||
|
||
[v8-perf]: http://v8project.blogspot.se/2017/01/speeding-up-v8-regular-expressions.html
|
||
|
||
|
||
### Version 2.0.0 (2016-06-19) ###
|
||
|
||
- Added: Support for ES2016. In other words, support for the `**` exponentiation
|
||
operator.
|
||
|
||
These are the breaking changes:
|
||
|
||
- `'**'.match(jsTokens)` no longer returns `['*', '*']`, but `['**']`.
|
||
- `'**='.match(jsTokens)` no longer returns `['*', '*=']`, but `['**=']`.
|
||
|
||
|
||
### Version 1.0.3 (2016-03-27) ###
|
||
|
||
- Improved: Made the regex ever so slightly smaller.
|
||
- Updated: The readme.
|
||
|
||
|
||
### Version 1.0.2 (2015-10-18) ###
|
||
|
||
- Improved: Limited npm package contents for a smaller download. Thanks to
|
||
@zertosh!
|
||
|
||
|
||
### Version 1.0.1 (2015-06-20) ###
|
||
|
||
- Fixed: Declared an undeclared variable.
|
||
|
||
|
||
### Version 1.0.0 (2015-02-26) ###
|
||
|
||
- Changed: Merged the 'operator' and 'punctuation' types into 'punctuator'. That
|
||
type is now equivalent to the Punctuator token in the ECMAScript
|
||
specification. (Backwards-incompatible change.)
|
||
- Fixed: A `-` followed by a number is now correctly matched as a punctuator
|
||
followed by a number. It used to be matched as just a number, but there is no
|
||
such thing as negative number literals. (Possibly backwards-incompatible
|
||
change.)
|
||
|
||
|
||
### Version 0.4.1 (2015-02-21) ###
|
||
|
||
- Added: Support for the regex `u` flag.
|
||
|
||
|
||
### Version 0.4.0 (2015-02-21) ###
|
||
|
||
- Improved: `jsTokens.matchToToken` performance.
|
||
- Added: Support for octal and binary number literals.
|
||
- Added: Support for template strings.
|
||
|
||
|
||
### Version 0.3.1 (2015-01-06) ###
|
||
|
||
- Fixed: Support for unicode spaces. They used to be allowed in names (which is
|
||
very confusing), and some unicode newlines were wrongly allowed in strings and
|
||
regexes.
|
||
|
||
|
||
### Version 0.3.0 (2014-12-19) ###
|
||
|
||
- Changed: The `jsTokens.names` array has been replaced with the
|
||
`jsTokens.matchToToken` function. The capturing groups of `jsTokens` are no
|
||
longer part of the public API; instead use said function. See this [gist] for
|
||
an example. (Backwards-incompatible change.)
|
||
- Changed: The empty string is now considered an “invalid” token, instead an
|
||
“empty” token (its own group). (Backwards-incompatible change.)
|
||
- Removed: component support. (Backwards-incompatible change.)
|
||
|
||
[gist]: https://gist.github.com/lydell/be49dbf80c382c473004
|
||
|
||
|
||
### Version 0.2.0 (2014-06-19) ###
|
||
|
||
- Changed: Match ES6 function arrows (`=>`) as an operator, instead of its own
|
||
category (“functionArrow”), for simplicity. (Backwards-incompatible change.)
|
||
- Added: ES6 splats (`...`) are now matched as an operator (instead of three
|
||
punctuations). (Backwards-incompatible change.)
|
||
|
||
|
||
### Version 0.1.0 (2014-03-08) ###
|
||
|
||
- Initial release.
|