@dabalabs/lang 0.0.1-beta → 0.0.2-beta

package/dist/dabalang.d.cts

@@ -51,6 +51,12 @@ interface LanguageConfig {
     pathPrefix: string | null;
     /** Language applied on un-prefixed paths when path routing is on. */
     isDefault: boolean;
+    /** False while the language is still being populated. The switcher
+     * omits it, so a visitor is never offered a language that would
+     * translate the page live in front of them. Absent (older gateways)
+     * counts as ready — a widget must not hide working languages because
+     * the server predates the field. */
+    ready: boolean;
 }
 interface ProjectMetadata {
     projectId: string;
@@ -94,6 +100,16 @@ declare class DabaLang {
      * with a prefix match, the widget never machine-translates that page.
      * (A prefix-less developer language instead swaps its uploaded
      * catalogue in place.) */
+    /** Target languages that actually have translations behind them.
+     *
+     * A configured-but-unpopulated language is worse than a missing one: a
+     * visitor picks it and watches the page translate live, paragraph by
+     * paragraph, or lands on a half-translated page while a run is still
+     * going. Languages with no config row at all are legacy
+     * target_languages entries that predate per-language config — they are
+     * shown, because hiding a language that has been serving traffic would
+     * be a regression. */
+    private readyLanguages;
     private isSiteTranslated;
     private selectLanguage;
     /** Overridable seam for tests — jsdom can't perform real navigation. */

package/dist/dabalang.d.ts

@@ -51,6 +51,12 @@ interface LanguageConfig {
     pathPrefix: string | null;
     /** Language applied on un-prefixed paths when path routing is on. */
     isDefault: boolean;
+    /** False while the language is still being populated. The switcher
+     * omits it, so a visitor is never offered a language that would
+     * translate the page live in front of them. Absent (older gateways)
+     * counts as ready — a widget must not hide working languages because
+     * the server predates the field. */
+    ready: boolean;
 }
 interface ProjectMetadata {
     projectId: string;
@@ -94,6 +100,16 @@ declare class DabaLang {
      * with a prefix match, the widget never machine-translates that page.
      * (A prefix-less developer language instead swaps its uploaded
      * catalogue in place.) */
+    /** Target languages that actually have translations behind them.
+     *
+     * A configured-but-unpopulated language is worse than a missing one: a
+     * visitor picks it and watches the page translate live, paragraph by
+     * paragraph, or lands on a half-translated page while a run is still
+     * going. Languages with no config row at all are legacy
+     * target_languages entries that predate per-language config — they are
+     * shown, because hiding a language that has been serving traffic would
+     * be a regression. */
+    private readyLanguages;
     private isSiteTranslated;
     private selectLanguage;
     /** Overridable seam for tests — jsdom can't perform real navigation. */

package/dist/dabalang.js

@@ -95,7 +95,10 @@ async function fetchProjectMetadata(gatewayUrl, projectId, apiKey) {
       code: l.code,
       provider: l.provider,
       pathPrefix: l.path_prefix,
-      isDefault: l.is_default
+      isDefault: l.is_default,
+      // Absent means an older gateway that has no readiness concept —
+      // treat as ready rather than hiding every language.
+      ready: l.ready ?? true
     }))
   };
 }
@@ -629,10 +632,14 @@ function injectStyles() {
   display: inline-flex;
   align-items: center;
   gap: 6px;
-  border: 1px solid rgba(0, 0, 0, 0.12);
-  background: #ffffff;
-  color: rgba(0, 0, 0, 0.75);
-  border-radius: 999px;
+  border: 1px solid var(--dabalang-border-color, rgba(0, 0, 0, 0.12));
+  background: var(--dabalang-bg, #ffffff);
+  color: var(--dabalang-color, rgba(0, 0, 0, 0.75));
+  /* Themeable so the switcher can match the host's own buttons. A widget
+     cannot know whether a site uses pills or 6px corners, and defaulting
+     to a pill made this the one control on the page that did not match.
+     Set --dabalang-radius on any ancestor to align it. */
+  border-radius: var(--dabalang-radius, 999px);
   padding: 6px 12px;
   cursor: pointer;
   font-family: -apple-system, BlinkMacSystemFont, "Segoe UI", Roboto, sans-serif;
@@ -899,8 +906,10 @@ function injectStyles() {
   max-height: 320px;
   overflow-y: auto;
   background: #ffffff;
-  border: 1px solid rgba(0, 0, 0, 0.1);
-  border-radius: 14px;
+  border: 1px solid var(--dabalang-border-color, rgba(0, 0, 0, 0.1));
+  /* Panel corners follow the trigger's family, one step softer, so a
+     square-cornered host does not get a pill-shaped dropdown. */
+  border-radius: var(--dabalang-panel-radius, 14px);
   box-shadow: 0 12px 32px rgba(0, 0, 0, 0.14);
   padding: 6px;
   box-sizing: border-box;
@@ -1255,7 +1264,7 @@ var DabaLang = class {
     });
     this.switcher = renderLanguageSwitcher(
       this.container,
-      this.metadata.targetLanguages,
+      this.readyLanguages(),
       this.metadata.sourceLang,
       (langCode) => {
         void this.selectLanguage(langCode);
@@ -1283,6 +1292,22 @@ var DabaLang = class {
    * with a prefix match, the widget never machine-translates that page.
    * (A prefix-less developer language instead swaps its uploaded
    * catalogue in place.) */
+  /** Target languages that actually have translations behind them.
+   *
+   * A configured-but-unpopulated language is worse than a missing one: a
+   * visitor picks it and watches the page translate live, paragraph by
+   * paragraph, or lands on a half-translated page while a run is still
+   * going. Languages with no config row at all are legacy
+   * target_languages entries that predate per-language config — they are
+   * shown, because hiding a language that has been serving traffic would
+   * be a regression. */
+  readyLanguages() {
+    const configs = this.metadata?.languages ?? [];
+    return (this.metadata?.targetLanguages ?? []).filter((code) => {
+      const config = configs.find((l) => l.code === code);
+      return config ? config.ready : true;
+    });
+  }
   isSiteTranslated(langCode) {
     const config = this.metadata?.languages.find((l) => l.code === langCode);
     return config?.provider === "developer";