tftsr-devops_investigation/node_modules/webdriverio/build/commands/element/shadow$.d.ts
Shaun Arman 8839075805 feat: initial implementation of TFTSR IT Triage & RCA application
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>
2026-03-14 22:36:25 -05:00

30 lines
1.1 KiB
TypeScript

/**
*
* Access an element inside a given element's shadowRoot. If you are working
* with lots of nested shadow roots, an alternative approach to `shadow$` is
* to use the [deep selector](https://webdriver.io/docs/selectors#deep-selectors).
*
* :::info
*
* WebdriverIO automatically pierces through shadow roots when using `$` or `$$` commands.
* This command is only needed if you automate within an environment that doesn't
* support WebDriver Bidi yet, e.g. mobile web testing with Appium.
*
* :::
*
* <example>
:shadow$$.js
it('should return an element inside a shadowRoot', async () => {
const innerEl = await $('custom-component').shadow$('#innerEl');
console.log(await innerEl.getValue()); // outputs: 'test123'
});
* </example>
*
* @alias element.shadow$
* @param {String|Function} selector selector or JS Function to fetch a certain element
* @return {WebdriverIO.Element}
* @type utility
*
*/
export declare function shadow$(this: WebdriverIO.Element, selector: string): Promise<WebdriverIO.Element | import("../../types.js").ChainablePromiseElement>;
//# sourceMappingURL=shadow$.d.ts.map