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>
84 lines
2.6 KiB
Markdown
84 lines
2.6 KiB
Markdown
# json-schema-traverse
|
|
Traverse JSON Schema passing each schema object to callback
|
|
|
|
[](https://travis-ci.org/epoberezkin/json-schema-traverse)
|
|
[](https://www.npmjs.com/package/json-schema-traverse)
|
|
[](https://coveralls.io/github/epoberezkin/json-schema-traverse?branch=master)
|
|
|
|
|
|
## Install
|
|
|
|
```
|
|
npm install json-schema-traverse
|
|
```
|
|
|
|
|
|
## Usage
|
|
|
|
```javascript
|
|
const traverse = require('json-schema-traverse');
|
|
const schema = {
|
|
properties: {
|
|
foo: {type: 'string'},
|
|
bar: {type: 'integer'}
|
|
}
|
|
};
|
|
|
|
traverse(schema, {cb});
|
|
// cb is called 3 times with:
|
|
// 1. root schema
|
|
// 2. {type: 'string'}
|
|
// 3. {type: 'integer'}
|
|
|
|
// Or:
|
|
|
|
traverse(schema, {cb: {pre, post}});
|
|
// pre is called 3 times with:
|
|
// 1. root schema
|
|
// 2. {type: 'string'}
|
|
// 3. {type: 'integer'}
|
|
//
|
|
// post is called 3 times with:
|
|
// 1. {type: 'string'}
|
|
// 2. {type: 'integer'}
|
|
// 3. root schema
|
|
|
|
```
|
|
|
|
Callback function `cb` is called for each schema object (not including draft-06 boolean schemas), including the root schema, in pre-order traversal. Schema references ($ref) are not resolved, they are passed as is. Alternatively, you can pass a `{pre, post}` object as `cb`, and then `pre` will be called before traversing child elements, and `post` will be called after all child elements have been traversed.
|
|
|
|
Callback is passed these parameters:
|
|
|
|
- _schema_: the current schema object
|
|
- _JSON pointer_: from the root schema to the current schema object
|
|
- _root schema_: the schema passed to `traverse` object
|
|
- _parent JSON pointer_: from the root schema to the parent schema object (see below)
|
|
- _parent keyword_: the keyword inside which this schema appears (e.g. `properties`, `anyOf`, etc.)
|
|
- _parent schema_: not necessarily parent object/array; in the example above the parent schema for `{type: 'string'}` is the root schema
|
|
- _index/property_: index or property name in the array/object containing multiple schemas; in the example above for `{type: 'string'}` the property name is `'foo'`
|
|
|
|
|
|
## Traverse objects in all unknown keywords
|
|
|
|
```javascript
|
|
const traverse = require('json-schema-traverse');
|
|
const schema = {
|
|
mySchema: {
|
|
minimum: 1,
|
|
maximum: 2
|
|
}
|
|
};
|
|
|
|
traverse(schema, {allKeys: true, cb});
|
|
// cb is called 2 times with:
|
|
// 1. root schema
|
|
// 2. mySchema
|
|
```
|
|
|
|
Without option `allKeys: true` callback will be called only with root schema.
|
|
|
|
|
|
## License
|
|
|
|
[MIT](https://github.com/epoberezkin/json-schema-traverse/blob/master/LICENSE)
|