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>
80 lines
1.7 KiB
Markdown
80 lines
1.7 KiB
Markdown
# once
|
|
|
|
Only call a function once.
|
|
|
|
## usage
|
|
|
|
```javascript
|
|
var once = require('once')
|
|
|
|
function load (file, cb) {
|
|
cb = once(cb)
|
|
loader.load('file')
|
|
loader.once('load', cb)
|
|
loader.once('error', cb)
|
|
}
|
|
```
|
|
|
|
Or add to the Function.prototype in a responsible way:
|
|
|
|
```javascript
|
|
// only has to be done once
|
|
require('once').proto()
|
|
|
|
function load (file, cb) {
|
|
cb = cb.once()
|
|
loader.load('file')
|
|
loader.once('load', cb)
|
|
loader.once('error', cb)
|
|
}
|
|
```
|
|
|
|
Ironically, the prototype feature makes this module twice as
|
|
complicated as necessary.
|
|
|
|
To check whether you function has been called, use `fn.called`. Once the
|
|
function is called for the first time the return value of the original
|
|
function is saved in `fn.value` and subsequent calls will continue to
|
|
return this value.
|
|
|
|
```javascript
|
|
var once = require('once')
|
|
|
|
function load (cb) {
|
|
cb = once(cb)
|
|
var stream = createStream()
|
|
stream.once('data', cb)
|
|
stream.once('end', function () {
|
|
if (!cb.called) cb(new Error('not found'))
|
|
})
|
|
}
|
|
```
|
|
|
|
## `once.strict(func)`
|
|
|
|
Throw an error if the function is called twice.
|
|
|
|
Some functions are expected to be called only once. Using `once` for them would
|
|
potentially hide logical errors.
|
|
|
|
In the example below, the `greet` function has to call the callback only once:
|
|
|
|
```javascript
|
|
function greet (name, cb) {
|
|
// return is missing from the if statement
|
|
// when no name is passed, the callback is called twice
|
|
if (!name) cb('Hello anonymous')
|
|
cb('Hello ' + name)
|
|
}
|
|
|
|
function log (msg) {
|
|
console.log(msg)
|
|
}
|
|
|
|
// this will print 'Hello anonymous' but the logical error will be missed
|
|
greet(null, once(msg))
|
|
|
|
// once.strict will print 'Hello anonymous' and throw an error when the callback will be called the second time
|
|
greet(null, once.strict(msg))
|
|
```
|