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>
91 lines
2.1 KiB
Markdown
91 lines
2.1 KiB
Markdown
# p-locate [](https://travis-ci.org/sindresorhus/p-locate)
|
|
|
|
> Get the first fulfilled promise that satisfies the provided testing function
|
|
|
|
Think of it like an async version of [`Array#find`](https://developer.mozilla.org/en/docs/Web/JavaScript/Reference/Global_Objects/Array/find).
|
|
|
|
|
|
## Install
|
|
|
|
```
|
|
$ npm install p-locate
|
|
```
|
|
|
|
|
|
## Usage
|
|
|
|
Here we find the first file that exists on disk, in array order.
|
|
|
|
```js
|
|
const pathExists = require('path-exists');
|
|
const pLocate = require('p-locate');
|
|
|
|
const files = [
|
|
'unicorn.png',
|
|
'rainbow.png', // Only this one actually exists on disk
|
|
'pony.png'
|
|
];
|
|
|
|
(async () => {
|
|
const foundPath = await pLocate(files, file => pathExists(file));
|
|
|
|
console.log(foundPath);
|
|
//=> 'rainbow'
|
|
})();
|
|
```
|
|
|
|
*The above is just an example. Use [`locate-path`](https://github.com/sindresorhus/locate-path) if you need this.*
|
|
|
|
|
|
## API
|
|
|
|
### pLocate(input, tester, [options])
|
|
|
|
Returns a `Promise` that is fulfilled when `tester` resolves to `true` or the iterable is done, or rejects if any of the promises reject. The fulfilled value is the current iterable value or `undefined` if `tester` never resolved to `true`.
|
|
|
|
#### input
|
|
|
|
Type: `Iterable<Promise | unknown>`
|
|
|
|
An iterable of promises/values to test.
|
|
|
|
#### tester(element)
|
|
|
|
Type: `Function`
|
|
|
|
This function will receive resolved values from `input` and is expected to return a `Promise<boolean>` or `boolean`.
|
|
|
|
#### options
|
|
|
|
Type: `Object`
|
|
|
|
##### concurrency
|
|
|
|
Type: `number`<br>
|
|
Default: `Infinity`<br>
|
|
Minimum: `1`
|
|
|
|
Number of concurrently pending promises returned by `tester`.
|
|
|
|
##### preserveOrder
|
|
|
|
Type: `boolean`<br>
|
|
Default: `true`
|
|
|
|
Preserve `input` order when searching.
|
|
|
|
Disable this to improve performance if you don't care about the order.
|
|
|
|
|
|
## Related
|
|
|
|
- [p-map](https://github.com/sindresorhus/p-map) - Map over promises concurrently
|
|
- [p-filter](https://github.com/sindresorhus/p-filter) - Filter promises concurrently
|
|
- [p-any](https://github.com/sindresorhus/p-any) - Wait for any promise to be fulfilled
|
|
- [More…](https://github.com/sindresorhus/promise-fun)
|
|
|
|
|
|
## License
|
|
|
|
MIT © [Sindre Sorhus](https://sindresorhus.com)
|