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>
62 lines
2.3 KiB
Markdown
62 lines
2.3 KiB
Markdown
# querystringify
|
|
|
|
[](https://www.npmjs.com/package/querystringify)[](https://travis-ci.org/unshiftio/querystringify)[](https://david-dm.org/unshiftio/querystringify)[](https://coveralls.io/r/unshiftio/querystringify?branch=master)
|
|
|
|
A somewhat JSON compatible interface for query string parsing. This query string
|
|
parser is dumb, don't expect to much from it as it only wants to parse simple
|
|
query strings. If you want to parse complex, multi level and deeply nested
|
|
query strings then you should ask your self. WTF am I doing?
|
|
|
|
## Installation
|
|
|
|
This module is released in npm as `querystringify`. It's also compatible with
|
|
`browserify` so it can be used on the server as well as on the client. To
|
|
install it simply run the following command from your CLI:
|
|
|
|
```
|
|
npm install --save querystringify
|
|
```
|
|
|
|
## Usage
|
|
|
|
In the following examples we assume that you've already required the library as:
|
|
|
|
```js
|
|
'use strict';
|
|
|
|
var qs = require('querystringify');
|
|
```
|
|
|
|
### qs.parse()
|
|
|
|
The parse method transforms a given query string in to an object. Parameters
|
|
without values are set to empty strings. It does not care if your query string
|
|
is prefixed with a `?`, a `#`, or not prefixed. It just extracts the parts
|
|
between the `=` and `&`:
|
|
|
|
```js
|
|
qs.parse('?foo=bar'); // { foo: 'bar' }
|
|
qs.parse('#foo=bar'); // { foo: 'bar' }
|
|
qs.parse('foo=bar'); // { foo: 'bar' }
|
|
qs.parse('foo=bar&bar=foo'); // { foo: 'bar', bar: 'foo' }
|
|
qs.parse('foo&bar=foo'); // { foo: '', bar: 'foo' }
|
|
```
|
|
|
|
### qs.stringify()
|
|
|
|
This transforms a given object in to a query string. By default we return the
|
|
query string without a `?` prefix. If you want to prefix it by default simply
|
|
supply `true` as second argument. If it should be prefixed by something else
|
|
simply supply a string with the prefix value as second argument:
|
|
|
|
```js
|
|
qs.stringify({ foo: bar }); // foo=bar
|
|
qs.stringify({ foo: bar }, true); // ?foo=bar
|
|
qs.stringify({ foo: bar }, '#'); // #foo=bar
|
|
qs.stringify({ foo: '' }, '&'); // &foo=
|
|
```
|
|
|
|
## License
|
|
|
|
MIT
|