HSLG Media

native-build.js

native-build.js

Source file: wordpress/hslg-presentation/assets/native-build.js

Module: wordpress-hslg-presentation

Size: 79 lines

SHA-256: af23075aff78b7c328d7ff7caf296bf9aea40a845bbca1a8d897482d22c0d4fd

Responsibility

Embeds a browser-only demonstration of the shared UI. Never belongs to a native APK.

Declared entry points

  • c — source line 4.
  • retryAdmin — source line 6.
  • retry — source line 7.
  • form — source line 10.
  • response — source line 11.
  • result — source line 12.
  • overlay — source line 22.
  • $ — source line 37.
  • closed — source line 38.
  • url — source line 39.
  • dismiss — source line 42.
  • form — source line 45.
  • poll — source line 49.
  • response — source line 52.
  • result — source line 54.
  • j — source line 56.
  • names — source line 59.
  • log — source line 63.
  • links — source line 65.
  • a — source line 66.
  • b — source line 67.
  • a — source line 68.

Imports and dependencies

No direct import declarations detected in this file.

Behaviour and audit locations

  • Line 11: const response = await fetch(c.ajax,{method:'POST',credentials:'same-origin',body:form});
  • Line 46: try { await fetch(c.ajax,{method:'POST',credentials:'same-origin',body:form}); } catch (_e) { /* UI dismissal is non-critical. */ }
  • Line 52: const response = await fetch(${c.ajax}?action=hslg_build_status&nonce=${encodeURIComponent(c.nonce)}&ts=${Date.now()}, {credentials:'same-origin',cache:'no-store'});

Relationship to the system

This page is the file-level source reference, not the architecture rationale. Read the module explanation, the corresponding architecture decision and user guide before changing behaviour. Names and line locations above are extracted from this exact source version; they are reference points, not proof that an external service or a phone feature works.

Change verification

Review the entry points and errors in this file, then run the module’s associated tests, source dependency gate, history gate and documentation coverage check. If the file changes an API response, user interaction, data model, deployment or third-party dependency, revise those human explanations and disaster recovery/licensing when relevant. Do not infer actual native or external API operation from source presence.