@campminder/components 0.1.0

package/dist/state-Ns9O6R8g.js

@@ -0,0 +1,12 @@
+import { n as r } from "./property-B5JHHBCF.js";
+/**
+ * @license
+ * Copyright 2017 Google LLC
+ * SPDX-License-Identifier: BSD-3-Clause
+ */
+function n(t) {
+  return r({ ...t, state: !0, attribute: !1 });
+}
+export {
+  n as r
+};

package/dist/super-user-banner/SuperUserBanner.d.ts

@@ -0,0 +1,43 @@
+import { LitElement } from 'lit';
+
+/**
+ * `<cm-super-user-banner>` — the impersonation / non-production banner.
+ *
+ * Ported Floor 8, 2026-09-08, from core-js's `Banner.ts` (`<super-user-banner>`).
+ * Renamed per the 2026-09-02 amendment: nothing in this repo consumes what upstream's
+ * build serves, so the port is free to take this repo's naming. The old tag and
+ * attribute names are recorded in the package `README.md` for whoever cuts the monolith
+ * over.
+ *
+ * What did not come across, and why, is in `SuperUserBanner.styles.ts` — the fixed
+ * positioning and the `ResizeObserver`, both because the shell owns layout.
+ */
+export declare class SuperUserBanner extends LitElement {
+    static readonly styles: import('lit').CSSResult;
+    client: string;
+    superUser: string;
+    activeEnvironment: string;
+    /**
+     * Which badge the environment gets, of three.
+     *
+     * **Upstream had two and failed open**: anything that was not exactly `staging` got
+     * the calm `local` badge. That is the wrong direction for a status indicator, and it
+     * was reachable rather than theoretical — the host emits this banner whenever
+     * `IsStaging || IsDevMachine || user is ICMMUser`, so a super-user impersonating
+     * someone **in production** gets it with `activeEnvironment="production"`, and
+     * upstream rendered that identically to a laptop. `undefined` — what
+     * `GetEnvironmentName()` returns when it cannot identify the host — did the same.
+     *
+     * So the unrecognised case now fails **loud**: only a known-quiet name gets the quiet
+     * badge, and everything else lands on `alert`. A new test tier added upstream will
+     * therefore over-warn until it is added to the pattern above, which is the failure
+     * direction to prefer for a banner whose entire job is to be noticed.
+     */
+    private get environmentBadgeClass();
+    render(): import('lit').TemplateResult<1>;
+}
+declare global {
+    interface HTMLElementTagNameMap {
+        'cm-super-user-banner': SuperUserBanner;
+    }
+}

package/dist/super-user-banner/SuperUserBanner.styles.d.ts

@@ -0,0 +1,21 @@
+/**
+ * Two things upstream did are gone, and the reasons are recorded once each — here,
+ * because this file is where the replacement lives. Everything else that references
+ * them links to this file rather than restating it.
+ *
+ * **`position: fixed; top: 0; left: 0; width: 100%`.** It took the banner out of flow
+ * entirely, which is why `ReactAppController` also has to emit a `hasSuperUserBanner`
+ * class and prepend container markup — a page must be pushed down behind an element
+ * occupying no space. The shell gives the banner an `auto` grid row, so declaring a
+ * height is now the whole contract. `display: block` below is load-bearing rather than
+ * incidental: a custom element is `display: inline` by default, and upstream's height
+ * only took effect because `position: fixed` forces block-level layout.
+ *
+ * **The `ResizeObserver`.** It compared `scrollWidth` against `window.innerWidth` and
+ * toggled an `overflowed` class. Two reasons it is not missed: the comparison was
+ * against the *window*, which stopped being the banner's own width the moment the shell
+ * owned layout; and the observer was constructed in `connectedCallback` but only ever
+ * attached in `firstUpdated`, which Lit runs once per instance, so a disconnect and
+ * reconnect left a live observer watching nothing.
+ */
+export declare const SuperUserBannerStyles: import('lit').CSSResult;

package/dist/super-user-banner/index.d.ts

@@ -0,0 +1,2 @@
+
+export { SuperUserBanner } from './SuperUserBanner';

package/dist/super-user-banner/super-user-banner.test.d.ts

@@ -0,0 +1 @@
+

package/dist/super-user-banner.d.ts

@@ -0,0 +1 @@
+export * from './super-user-banner/index'

package/dist/super-user-banner.js

@@ -0,0 +1,178 @@
+import { i as p, n as h, a as g, b as d, t as c } from "./property-B5JHHBCF.js";
+const b = p`
+  * {
+    padding: 0;
+    margin: 0;
+    box-sizing: border-box;
+  }
+
+  :host {
+    display: block;
+    height: 32px;
+    min-height: 32px;
+    max-height: 32px;
+  }
+
+  .banner {
+    height: inherit;
+    min-height: inherit;
+    max-height: inherit;
+    background-color: rgb(40, 40, 40);
+    display: flex;
+    overflow-x: auto;
+  }
+
+  /*
+   * Centred when the content fits, flush-left when it does not: auto margins collapse
+   * to zero once there is no free space, so the start of the content stays reachable
+   * instead of being clipped off the left edge.
+   */
+  .content {
+    display: flex;
+    flex-wrap: nowrap;
+    align-items: center;
+    gap: 1rem;
+    margin: auto;
+    padding: 0 8px;
+    white-space: nowrap;
+    /*
+     * Load-bearing, and measured. Without it '.content' grows unbounded inside the
+     * scroll container, so the names never come under pressure and never ellipsize --
+     * the badge just leaves the viewport instead. Constraining the row to the banner
+     * is what makes the shrinking below actually happen.
+     */
+    max-width: 100%;
+  }
+
+  .banner-text {
+    font-family: 'Inter', sans-serif;
+    font-size: 14px;
+    font-weight: 400;
+    line-height: 20px;
+    letter-spacing: -0.001em;
+    color: rgba(240, 240, 240, 1);
+  }
+
+  /*
+   * The names give up space before the badge does.
+   *
+   * This banner exists to make the environment and the impersonation unmistakable, and
+   * the badge is the last flex child -- so without this, a merely long client name (a
+   * real org name is enough; no attacker required) pushes the badge out of view. The
+   * names truncate with an ellipsis instead, which loses nothing that is not still
+   * visible in the page itself.
+   */
+  .name {
+    min-width: 0;
+    overflow: hidden;
+    text-overflow: ellipsis;
+  }
+
+  .text-bold {
+    font-weight: 600;
+  }
+
+  .environment-badge {
+    flex-shrink: 0;
+    height: 24px;
+    border-radius: 12px;
+    padding: 2px 8px;
+    text-transform: uppercase;
+    font-size: 14px;
+    font-weight: 600;
+    line-height: 20px;
+    letter-spacing: 0.0025em;
+    text-align: left;
+  }
+
+  .staging-badge {
+    background: rgba(206, 52, 0, 1);
+    color: rgba(240, 240, 240, 1);
+  }
+
+  .local-badge {
+    color: rgba(119, 61, 189, 1);
+    background: rgba(240, 240, 240, 1);
+  }
+
+  /*
+   * The loud one, for 'production' and for an environment nobody recognises. Deliberately
+   * not styled like 'staging': a staging session is expected, and these two are the
+   * cases where someone should stop and look. See 'environmentBadgeClass' for which
+   * values land here and why.
+   */
+  .alert-badge {
+    background: rgba(140, 0, 0, 1);
+    color: rgba(255, 240, 240, 1);
+    box-shadow: 0 0 0 2px rgba(255, 200, 200, 0.9);
+  }
+
+  /* Narrow enough that the label costs more than it explains. */
+  @media (max-width: 530px) {
+    .user-label {
+      display: none;
+    }
+  }
+`;
+var m = Object.defineProperty, u = Object.getOwnPropertyDescriptor, i = (n, a, r, s) => {
+  for (var e = s > 1 ? void 0 : s ? u(a, r) : a, o = n.length - 1, l; o >= 0; o--)
+    (l = n[o]) && (e = (s ? l(a, r, e) : l(e)) || e);
+  return s && e && m(a, r, e), e;
+};
+const x = /^(local|localhost|dev|develop(ment)?|qa\d*|test\d*|demo|sandbox|uat)$/;
+let t = class extends g {
+  constructor() {
+    super(...arguments), this.client = "", this.superUser = "", this.activeEnvironment = "";
+  }
+  /**
+   * Which badge the environment gets, of three.
+   *
+   * **Upstream had two and failed open**: anything that was not exactly `staging` got
+   * the calm `local` badge. That is the wrong direction for a status indicator, and it
+   * was reachable rather than theoretical — the host emits this banner whenever
+   * `IsStaging || IsDevMachine || user is ICMMUser`, so a super-user impersonating
+   * someone **in production** gets it with `activeEnvironment="production"`, and
+   * upstream rendered that identically to a laptop. `undefined` — what
+   * `GetEnvironmentName()` returns when it cannot identify the host — did the same.
+   *
+   * So the unrecognised case now fails **loud**: only a known-quiet name gets the quiet
+   * badge, and everything else lands on `alert`. A new test tier added upstream will
+   * therefore over-warn until it is added to the pattern above, which is the failure
+   * direction to prefer for a banner whose entire job is to be noticed.
+   */
+  get environmentBadgeClass() {
+    const n = this.activeEnvironment.trim().toLowerCase();
+    return n === "staging" ? "staging" : x.test(n) ? "local" : "alert";
+  }
+  render() {
+    return d`
+      <section class="banner banner-text">
+        <div class="content">
+          <span class="text-bold name"
+            ><span class="user-label">Logged in as:</span> ${this.superUser}</span
+          >
+          <span class="text-bold name">Client: ${this.client}</span>
+          <span class="environment-badge ${this.environmentBadgeClass}-badge"
+            >${this.activeEnvironment}</span
+          >
+        </div>
+      </section>
+    `;
+  }
+};
+t.styles = b;
+i([
+  h({ type: String })
+], t.prototype, "client", 2);
+i([
+  h({ type: String, attribute: "super-user" })
+], t.prototype, "superUser", 2);
+i([
+  h({ type: String, attribute: "active-environment" })
+], t.prototype, "activeEnvironment", 2);
+t = i([
+  c("cm-super-user-banner")
+], t);
+export {
+  t as SuperUserBanner
+};

package/dist/top-bar/TopBar.d.ts

@@ -0,0 +1,39 @@
+import { LitElement } from 'lit';
+import { Data } from './Utils/types';
+
+/**
+ * `<cm-top-bar>` — the top navigation bar.
+ *
+ * Ported Floor 7, 2026-09-08, from core-js's `TopBar.ts` (`<top-bar>`). Search is a
+ * named `<slot>` rather than a registry-name probe for `search-bar`, all CDN script
+ * loading is gone, and the shell owns layout — this component sets no inline
+ * position on its own section and reads no side-nav state out of `localStorage`.
+ * See the package `README.md` for the full list of what did not come across.
+ */
+export declare class TopBar extends LitElement {
+    static readonly styles: import('lit').CSSResult;
+    data: Data | null;
+    isDropdownOpen: boolean;
+    isSuperUserDropdownOpen: boolean;
+    connectedCallback(): void;
+    disconnectedCallback(): void;
+    private initEventListeners;
+    private removeEventListeners;
+    private handleOutsideClick;
+    private closeAllDropdowns;
+    private toggleDropdown;
+    private toggleSuperUserDropdown;
+    private renderFeatureValue;
+    private renderFeature;
+    private renderFeatureSection;
+    private renderSearch;
+    private renderNavigationLink;
+    private renderSuperUserDropdown;
+    private renderUserDropdown;
+    render(): import('lit').TemplateResult<1>;
+}
+declare global {
+    interface HTMLElementTagNameMap {
+        'cm-top-bar': TopBar;
+    }
+}

package/dist/top-bar/TopBar.styles.d.ts

@@ -0,0 +1 @@
+export declare const TopBarStyles: import('lit').CSSResult;

package/dist/top-bar/Utils/helpers.d.ts

@@ -0,0 +1,3 @@
+import { Data } from './types';
+
+export declare const decodeString: (dataString64: string) => Data | null;

package/dist/top-bar/Utils/safe-url.d.ts

@@ -0,0 +1,56 @@
+/**
+ * Guards for host-supplied URLs and markup.
+ *
+ * Lit escapes text and attribute *content*, but it does not police URL *schemes*:
+ * `href="javascript:…"` is a valid attribute value as far as a template is concerned,
+ * and it executes on click. That is the gap these functions close.
+ *
+ * The values they guard arrive in the `data` property, which is a base64 HTML
+ * attribute — so every one of them crosses a boundary this component cannot see the
+ * other side of, and this package is meant to publish, which makes "the host" whoever
+ * installs it. Treating that input as trusted is not available to us.
+ */
+/** What a refused URL becomes. */
+export declare const REFUSED_HREF = "#";
+/**
+ * Whether `url` is safe to navigate to.
+ *
+ * Callers that need the yes/no answer must use this rather than comparing a returned
+ * value against `REFUSED_HREF` — a link whose URL is legitimately `'#'` is refused by
+ * that comparison and not by this function, and the two answers must not diverge.
+ */
+export declare function isNavigable(url: string | undefined | null): boolean;
+/**
+ * Returns `url` if it is safe to put in an `href`, and `'#'` if it is not.
+ *
+ * The original string is returned rather than the parsed `href`, deliberately:
+ * normalising would resolve every relative URL against `PARSE_BASE` and rewrite
+ * `/camper/list` into `https://portal.invalid/camper/list`, breaking the majority of
+ * this chrome's links. Only the scheme needs to survive parsing, and `new URL()`
+ * implements the same WHATWG algorithm the browser applies to the attribute later, so
+ * the check and the eventual consumer agree on what the scheme is.
+ */
+export declare function safeHref(url: string | undefined | null): string;
+/**
+ * Returns `url` if it is safe to put in an `<img src>`, and `''` if it is not.
+ *
+ * A `javascript:` URL in `src` does not execute in any current browser, so this is
+ * about egress rather than execution: an image source is an outbound request to a host
+ * of the data's choosing, made automatically on render. Pair it with
+ * `referrerpolicy="no-referrer"` at the call site so the request carries no page URL.
+ */
+export declare function safeImageSrc(url: string | undefined | null): string;
+export declare function safePopupFeatures(features: string | undefined | null): string;
+/**
+ * Splits a value on `<br>` so the pieces can be rendered as text with real line breaks.
+ *
+ * This exists to retire lit's `unsafeHTML`. Upstream ran `feature.value` through it
+ * after a `.replace(/<br>/g, '<br/>')`, which says plainly what the directive was for:
+ * line breaks. Nothing else in the value was ever meant to be markup, so nothing else
+ * needs to be — the caller renders these segments as text, and lit escapes them.
+ *
+ * The pattern accepts attributes (`<br class="x">`) because upstream's HTML parser did,
+ * and a variant that failed to match would silently lose a line break rather than
+ * failing loudly.
+ */
+export declare function splitOnLineBreaks(value: string | undefined | null): string[];

package/dist/top-bar/Utils/safe-url.test.d.ts

@@ -0,0 +1 @@
+export {};

package/dist/top-bar/Utils/types.d.ts

@@ -0,0 +1,50 @@
+export interface Data {
+    logo_url: string;
+    page_title: string;
+    account_data: AccountData;
+    client_data: ClientData;
+    reset_password_url: string;
+    super_user_data?: SuperUserData | null;
+}
+export interface AccountData {
+    person_data: PersonData;
+    links: Link[];
+}
+export interface PersonData {
+    id: number;
+    name: string;
+    profile_url: string;
+}
+export interface Link {
+    name: string;
+    url: string;
+    icon_url: string;
+    sort_order: number;
+    popup?: boolean;
+    popup_properties?: string;
+    new_tab?: boolean;
+}
+export interface ClientData {
+    id: number;
+    name: string;
+    domain: string;
+    current_season_id: number;
+    country: string;
+}
+export interface Feature {
+    name?: string;
+    value?: string;
+    enabled?: boolean;
+    display?: 'inline' | 'block';
+    sort_order: number;
+}
+export interface FeatureSection {
+    title?: string;
+    sub_title?: string;
+    icon_url?: string;
+    sort_order: number;
+    features: Feature[];
+}
+export interface SuperUserData {
+    sections: FeatureSection[];
+}

package/dist/top-bar/assets/TopBarIcons/CheckIcon.d.ts

@@ -0,0 +1,2 @@
+declare const _default: import('lit').TemplateResult<1>;
+export default _default;

package/dist/top-bar/assets/TopBarIcons/CrossIcon.d.ts

@@ -0,0 +1,2 @@
+declare const _default: import('lit').TemplateResult<1>;
+export default _default;

package/dist/top-bar/assets/TopBarIcons/DropDownIcon.d.ts

@@ -0,0 +1,2 @@
+declare const _default: import('lit').TemplateResult<1>;
+export default _default;

package/dist/top-bar/assets/TopBarIcons/InfoIcon.d.ts

@@ -0,0 +1,2 @@
+declare const _default: import('lit').TemplateResult<1>;
+export default _default;

package/dist/top-bar/assets/TopBarIcons/OpenInNewIcon.d.ts

@@ -0,0 +1,2 @@
+declare const _default: import('lit').TemplateResult<1>;
+export default _default;

package/dist/top-bar/assets/TopBarIcons/index.d.ts

@@ -0,0 +1,7 @@
+import { default as CheckSvgIcon } from './CheckIcon';
+import { default as CrossSvgIcon } from './CrossIcon';
+import { default as DropDownSvgIcon } from './DropDownIcon';
+import { default as InfoSvgIcon } from './InfoIcon';
+import { default as OpenInNewSvgIcon } from './OpenInNewIcon';
+
+export { CheckSvgIcon, CrossSvgIcon, DropDownSvgIcon, InfoSvgIcon, OpenInNewSvgIcon };

package/dist/top-bar/index.d.ts

@@ -0,0 +1,3 @@
+
+export { TopBar } from './TopBar';
+export type { AccountData, ClientData, Data, Feature, FeatureSection, Link, PersonData, SuperUserData, } from './Utils/types';

package/dist/top-bar/top-bar.test.d.ts

@@ -0,0 +1 @@
+

package/dist/top-bar.d.ts

@@ -0,0 +1 @@
+export * from './top-bar/index'