📄 File detail

components/permissions/utils.ts

🧩 .ts📏 26 lines💾 660 bytes📝 text

🎯 Use case

This file lives under “components/”, which covers shared React UI pieces. On the API surface it exposes logUnaryPermissionEvent — mainly functions, hooks, or classes. It composes internal code from PermissionRequest (relative imports).

Generated from folder role, exports, dependency roots, and inline comments — not hand-reviewed for every path.

🧠 Inline summary

import { getHostPlatformForAnalytics } from '../../utils/env.js' import { type CompletionType, logUnaryEvent } from '../../utils/unaryLogging.js' import type { ToolUseConfirm } from './PermissionRequest.js' export function logUnaryPermissionEvent(

📤 Exports (heuristic)

logUnaryPermissionEvent

🖥️ Source preview

import { getHostPlatformForAnalytics } from '../../utils/env.js'
import { type CompletionType, logUnaryEvent } from '../../utils/unaryLogging.js'
import type { ToolUseConfirm } from './PermissionRequest.js'

export function logUnaryPermissionEvent(
  completion_type: CompletionType,
  {
    assistantMessage: {
      message: { id: message_id },
    },
  }: ToolUseConfirm,
  event: 'accept' | 'reject',
  hasFeedback?: boolean,
): void {
  void logUnaryEvent({
    completion_type,
    event,
    metadata: {
      language_name: 'none',
      message_id,
      platform: getHostPlatformForAnalytics(),
      hasFeedback: hasFeedback ?? false,
    },
  })
}