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>
71 lines
2.1 KiB
Markdown
71 lines
2.1 KiB
Markdown
# regenerate-unicode-properties [](https://www.npmjs.com/package/regenerate-unicode-properties)
|
|
|
|
_regenerate-unicode-properties_ is a collection of [Regenerate](https://github.com/mathiasbynens/regenerate) sets for [various Unicode properties](https://github.com/tc39/proposal-regexp-unicode-property-escapes).
|
|
|
|
## Installation
|
|
|
|
To use _regenerate-unicode-properties_ programmatically, install it as a dependency via [npm](https://www.npmjs.com/):
|
|
|
|
```bash
|
|
$ npm install regenerate-unicode-properties
|
|
```
|
|
|
|
## Usage
|
|
|
|
To get a map of supported properties and their values:
|
|
|
|
```js
|
|
const properties = require('regenerate-unicode-properties');
|
|
```
|
|
|
|
To get a specific Regenerate set:
|
|
|
|
```js
|
|
// Examples:
|
|
const Lu = require('regenerate-unicode-properties/General_Category/Uppercase_Letter.js').characters;
|
|
const Greek = require('regenerate-unicode-properties/Script_Extensions/Greek.js').characters;
|
|
```
|
|
|
|
Some properties can also refer to strings rather than single characters:
|
|
```js
|
|
const { characters, strings } = require('regenerate-unicode-properties/Property_of_Strings/Basic_Emoji.js');
|
|
```
|
|
|
|
To get the Unicode version the data was based on:
|
|
|
|
```js
|
|
const unicodeVersion = require('regenerate-unicode-properties/unicode-version.js');
|
|
```
|
|
|
|
## For maintainers
|
|
|
|
### How to publish a new release
|
|
|
|
1. On the `main` branch, bump the version number in `package.json`:
|
|
|
|
```sh
|
|
npm version patch -m 'Release v%s'
|
|
```
|
|
|
|
Instead of `patch`, use `minor` or `major` [as needed](https://semver.org/).
|
|
|
|
Note that this produces a Git commit + tag.
|
|
|
|
1. Push the release commit and tag:
|
|
|
|
```sh
|
|
git push && git push --tags
|
|
```
|
|
|
|
Our CI then automatically publishes the new release to npm.
|
|
|
|
## Author
|
|
|
|
| [](https://twitter.com/mathias "Follow @mathias on Twitter") |
|
|
|---|
|
|
| [Mathias Bynens](https://mathiasbynens.be/) |
|
|
|
|
## License
|
|
|
|
_regenerate-unicode-properties_ is available under the [MIT](https://mths.be/mit) license.
|