history-pane.ts File Reference

import html;

Functions
function	say (msg:string, kind:'ok'| 'err'='ok')
	Asked before the real values go on screen, because a screenshot keeps them.

Variables
const	$ = (id: string) => document.getElementById(id)!
	Tools -> Config history (Phase 35): the app side of unv history ....
project	__pad0__
project_name	__pad1__
exporter	__pad2__
at	__pad3__
sha256	__pad4__
bytes	__pad5__
cause	__pad6__

Function Documentation

say()

function say	(		msg:string,
			kind:'ok'| 'err' = 'ok'
	)

Asked before the real values go on screen, because a screenshot keeps them.

A file's text, from a picker created and removed per use (a static one is a WebKitGTK ghost). Reads a snapshot back into the project's chunks. The snapshot's real text is what was deployed, so this needs it unmasked; the question says what is replaced and that values arrive as literal text, not references.

Variable Documentation

$

const $ = (id: string) => document.getElementById(id)!

Tools -> Config history (Phase 35): the app side of unv history ....

The same dispatcher answers every surface: a local vault reaches it through the history_call command, a remote one through POST /api/history. The pane never renders anything itself, so what it shows is what unv history shows.

Default is the fingerprinted text, in which a rotated secret is a changed fingerprint. The real text appears only when Reveal is ticked and confirmed, and the Save button writes it to a file, not into the page.

__pad0__

project __pad0__

__pad1__

project_name __pad1__

__pad2__

exporter __pad2__

__pad3__

at __pad3__

__pad4__

sha256 __pad4__

__pad5__

bytes __pad5__

__pad6__

cause __pad6__