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>
82 lines
1.6 KiB
Markdown
82 lines
1.6 KiB
Markdown
# BSER Binary Serialization
|
|
|
|
BSER is a binary serialization scheme that can be used as an alternative to JSON.
|
|
BSER uses a framed encoding that makes it simpler to use to stream a sequence of
|
|
encoded values.
|
|
|
|
It is intended to be used for local-IPC only and strings are represented as binary
|
|
with no specific encoding; this matches the convention employed by most operating
|
|
system filename storage.
|
|
|
|
For more details about the serialization scheme see
|
|
[Watchman's docs](https://facebook.github.io/watchman/docs/bser.html).
|
|
|
|
## API
|
|
|
|
```js
|
|
var bser = require('bser');
|
|
```
|
|
|
|
### bser.loadFromBuffer
|
|
|
|
The is the synchronous decoder; given an input string or buffer,
|
|
decodes a single value and returns it. Throws an error if the
|
|
input is invalid.
|
|
|
|
```js
|
|
var obj = bser.loadFromBuffer(buf);
|
|
```
|
|
|
|
### bser.dumpToBuffer
|
|
|
|
Synchronously encodes a value as BSER.
|
|
|
|
```js
|
|
var encoded = bser.dumpToBuffer(['hello']);
|
|
console.log(bser.loadFromBuffer(encoded)); // ['hello']
|
|
```
|
|
|
|
### BunserBuf
|
|
|
|
The asynchronous decoder API is implemented in the BunserBuf object.
|
|
You may incrementally append data to this object and it will emit the
|
|
decoded values via its `value` event.
|
|
|
|
```js
|
|
var bunser = new bser.BunserBuf();
|
|
|
|
bunser.on('value', function(obj) {
|
|
console.log(obj);
|
|
});
|
|
```
|
|
|
|
Then in your socket `data` event:
|
|
|
|
```js
|
|
bunser.append(buf);
|
|
```
|
|
|
|
## Example
|
|
|
|
Read BSER from socket:
|
|
|
|
```js
|
|
var bunser = new bser.BunserBuf();
|
|
|
|
bunser.on('value', function(obj) {
|
|
console.log('data from socket', obj);
|
|
});
|
|
|
|
var socket = net.connect('/socket');
|
|
|
|
socket.on('data', function(buf) {
|
|
bunser.append(buf);
|
|
});
|
|
```
|
|
|
|
Write BSER to socket:
|
|
|
|
```js
|
|
socket.write(bser.dumpToBuffer(obj));
|
|
```
|