8839075805
Implements Phases 1-8 of the TFTSR implementation plan. Rust backend (Tauri 2.x, src-tauri/): - Multi-provider AI: OpenAI-compatible, Anthropic, Gemini, Mistral, Ollama - PII detection engine: 11 regex patterns with overlap resolution - SQLCipher AES-256 encrypted database with 10 versioned migrations - 28 Tauri IPC commands for triage, analysis, document, and system ops - Ollama: hardware probe, model recommendations, pull/delete with events - RCA and blameless post-mortem Markdown document generators - PDF export via printpdf - Audit log: SHA-256 hash of every external data send - Integration stubs for Confluence, ServiceNow, Azure DevOps (v0.2) Frontend (React 18 + TypeScript + Vite, src/): - 9 pages: full triage workflow NewIssue→LogUpload→Triage→Resolution→RCA→Postmortem→History+Settings - 7 components: ChatWindow, TriageProgress, PiiDiffViewer, DocEditor, HardwareReport, ModelSelector, UI primitives - 3 Zustand stores: session, settings (persisted), history - Type-safe tauriCommands.ts matching Rust backend types exactly - 8 IT domain system prompts (Linux, Windows, Network, K8s, DB, Virt, HW, Obs) DevOps: - .woodpecker/test.yml: rustfmt, clippy, cargo test, tsc, vitest on every push - .woodpecker/release.yml: linux/amd64 + linux/arm64 builds, Gogs release upload Verified: - cargo check: zero errors - tsc --noEmit: zero errors - vitest run: 13/13 unit tests passing Co-Authored-By: Claude Sonnet 4.6 (1M context) <noreply@anthropic.com>
45 lines
1.7 KiB
TypeScript
45 lines
1.7 KiB
TypeScript
import type { Browser as PuppeteerBrowser } from 'puppeteer-core';
|
|
/**
|
|
* Get the [Puppeteer Browser instance](https://pptr.dev/#?product=Puppeteer&version=v5.1.0&show=api-class-browser)
|
|
* to run commands with Puppeteer. Note that all Puppeteer commands are
|
|
* asynchronous by default so in order to interchange between sync and async
|
|
* execution make sure to wrap your Puppeteer calls within a `browser.call`
|
|
* commands as shown in the example.
|
|
*
|
|
* :::info
|
|
*
|
|
* Note that using Puppeteer requires support for Chrome DevTools protocol and e.g.
|
|
* can not be used when running automated tests in the cloud. Chrome DevTools protocol is not installed by default,
|
|
* use `npm install puppeteer-core` to install it.
|
|
* Find out more in the [Automation Protocols](/docs/automationProtocols) section.
|
|
*
|
|
* :::
|
|
*
|
|
* :::info
|
|
*
|
|
* Note: Puppeteer is currently __not__ supported when running [component tests](/docs/component-testing).
|
|
*
|
|
* :::
|
|
*
|
|
* <example>
|
|
:getPuppeteer.test.js
|
|
it('should allow me to use Puppeteer', async () => {
|
|
// WebDriver command
|
|
await browser.url('https://webdriver.io')
|
|
|
|
const puppeteerBrowser = await browser.getPuppeteer()
|
|
// switch to Puppeteer
|
|
const metrics = await browser.call(async () => {
|
|
const pages = await puppeteerBrowser.pages()
|
|
pages[0].setGeolocation({ latitude: 59.95, longitude: 30.31667 })
|
|
return pages[0].metrics()
|
|
})
|
|
|
|
console.log(metrics.LayoutCount) // returns LayoutCount value
|
|
})
|
|
* </example>
|
|
*
|
|
* @return {PuppeteerBrowser} initiated puppeteer instance connected to the browser
|
|
*/
|
|
export declare function getPuppeteer(this: WebdriverIO.Browser): Promise<PuppeteerBrowser>;
|
|
//# sourceMappingURL=getPuppeteer.d.ts.map
|