/**
 * This Source Code is subject to the terms of the Mozilla Public
 * License, v. 2.0. If a copy of the MPL was not distributed with this
 * file, You can obtain one at http://mozilla.org/MPL/2.0/.
 *
 * Copyright (c) Infonomic Company Limited
 */

/**
 * Server-only lifecycle hooks for the `docs` collection.
 *
 * ──────────────────────────────────────────────────────────────────────────
 *  Why this file exists (the affordance)
 * ──────────────────────────────────────────────────────────────────────────
 * A collection *schema* (`./schema.ts`) is **isomorphic** — Byline bundles it
 * into the browser admin as well as the server, because the admin reads field
 * config from it. Anything the schema *statically imports* therefore ships to
 * the client. Hook *bodies*, however, only ever run server-side.
 *
 * Search indexing is the canonical reason this matters: it imports the
 * server-only client getters from `@byline/client/server`. Importing
 * that from the schema would drag server code into the browser bundle (fatal
 * in dev). The server bootstrap avoids it by registering these hooks from a
 * server-only module:
 *
 *     // collections/server-hooks.ts
 *     collections: { docs: () => import('./docs/hooks.js') }
 *
 * No client entry reaches that registry, so this file and its transitive graph
 * are structurally absent from the client bundle without a host-framework
 * transform. `@byline/core` attaches and resolves the loader on the server.
 * The upshot: **inside this file we may statically import server-only modules
 * directly.** See docs/04-collections → "Server-only hook registry".
 *
 * ──────────────────────────────────────────────────────────────────────────
 *  Search indexing
 * ──────────────────────────────────────────────────────────────────────────
 * Indexing rides the same lifecycle hooks. The orchestration lives in
 * `@byline/client`: `indexDocument` re-reads the *published* view per locale
 * and upserts / removes (so publish, unpublish, draft-over-published, and
 * plain edits all converge on the same idempotent path); `removeFromIndex`
 * drops every locale on delete.
 *
 * Resolve the client with `getSystemBylineClient()` (super-admin context, no
 * session cookies) — NOT the request-scoped `getAdminBylineClient()`.
 * Indexing is background maintenance that runs from out-of-band write paths
 * too (the import-docs script, seeds, migrations), where there is no HTTP
 * request to read a session cookie from. See
 * docs/06-search/index.md.
 */

import { defineHooks } from '@byline/core'
import { getSystemBylineClient } from '@byline/client/server'

export default defineHooks({
  beforeCreate: async ({ data, collectionPath }) => {
    console.log(`beforeCreate: creating a document in '${collectionPath}'`, data)
  },
  afterCreate: async ({ collectionPath, documentId, documentVersionId }) => {
    console.log(
      `afterCreate: document ${documentId} (version ${documentVersionId}) created in '${collectionPath}'`
    )
    await getSystemBylineClient().collection('docs').indexDocument(documentId)
  },
  beforeUpdate: async ({ data, collectionPath }) => {
    console.log(`beforeUpdate: updating a document in '${collectionPath}'`, data)
  },
  afterUpdate: async ({ collectionPath, documentId, documentVersionId }) => {
    console.log(
      `afterUpdate: document ${documentId} (version ${documentVersionId}) in '${collectionPath}' updated`
    )
    await getSystemBylineClient().collection('docs').indexDocument(documentId)
  },
  // Path and advertised-locale edits are immediate document-grain writes, not
  // content updates. Re-index their published view through this dedicated event.
  afterSystemFieldsChange: async ({ documentId, collectionPath, requested, changed }) => {
    console.log(
      `afterSystemFieldsChange: ${documentId} in '${collectionPath}' changed`,
      changed
    )
    // Advertised locales affect alternates/sitemaps, not indexed content.
    if (requested.path) {
      await getSystemBylineClient().collection('docs').indexDocument(documentId)
    }
  },
  beforeStatusChange: async ({ documentId, collectionPath, previousStatus, nextStatus }) => {
    console.log(
      `beforeStatusChange: ${documentId} in '${collectionPath}' ${previousStatus} → ${nextStatus}`
    )
  },
  // Publish / unpublish flow through the status lifecycle (not afterUpdate),
  // so re-index here too — this is when content becomes visible / invisible
  // to anonymous traffic.
  afterStatusChange: async ({ documentId, collectionPath, previousStatus, nextStatus }) => {
    console.log(
      `afterStatusChange: ${documentId} in '${collectionPath}' ${previousStatus} → ${nextStatus}`
    )
    await getSystemBylineClient().collection('docs').indexDocument(documentId)
  },
  beforeUnpublish: async ({ documentId, collectionPath }) => {
    console.log(`beforeUnpublish: unpublishing ${documentId} in '${collectionPath}'`)
  },
  afterUnpublish: async ({ documentId, collectionPath }) => {
    console.log(`afterUnpublish: ${documentId} in '${collectionPath}' unpublished`)
    await getSystemBylineClient().collection('docs').indexDocument(documentId)
  },
  beforeDelete: async ({ documentId, collectionPath }) => {
    console.log(`beforeDelete: deleting ${documentId} in '${collectionPath}'`)
  },
  afterDelete: async ({ documentId, collectionPath }) => {
    console.log(`afterDelete: ${documentId} in '${collectionPath}' deleted`)
    await getSystemBylineClient().collection('docs').removeFromIndex(documentId)
  },
  // Fires on any structural tree change (place / reorder / re-parent /
  // promote-on-delete) for a `tree: true` collection. The payload carries the
  // affected set; a docs site typically invalidates its nav / breadcrumb /
  // prev-next caches here. A tree move doesn't change a document's indexable
  // text, so there's nothing to re-index.
  afterTreeChange: async ({ collectionPath }) => {
    console.log(`afterTreeChange: tree structure changed in '${collectionPath}'`)
  },
})