@v-office/website-sdk 2.7.0 → 2.8.0

package/README.md

@@ -2,7 +2,10 @@
 
 Website-facing SDK facade for vOffice backends.
 
-Version 2.1.0 extends the 2.0.0 website SDK facade with v10 documents, contact validation/submission, voucher-aware search and quote output, and improved quote option availability.
+The 2.8.0 line adds the catalog-backed custom-attribute registry, backend-aware
+atomic filter compositions, and consistent custom-attribute display and highlight
+behavior.
+See `instructions/CHANGELOG.md` for the complete release history.
 
 ## Install
 
@@ -25,6 +28,7 @@ const sdk = createWebsiteSDK({
   config: {
     backend: "v10",
     apiEndpoint: "https://api.example.com/graphql",
+    searchEndpoint: "https://search.example.com/search",
     accessToken: "...",
     imageBaseUrl: "https://images.example.com",
   },
@@ -106,6 +110,7 @@ website-sdk --backend v10 --config ./website-sdk-config.json --options ./website
 For v10, environment configuration uses:
 
 - `VOFFICE_API_ENDPOINT`
+- `VOFFICE_SEARCH_ENDPOINT`
 - `VOFFICE_LOCAL_DEV_ACCESS_TOKEN`
 - `VOFFICE_IMAGE_BASE_URL`
 
@@ -127,4 +132,26 @@ The 2.0.0 line was the breaking migration from the legacy SDK API. If you are st
 - The error model now comes from `@v-office/sdk-core`.
 - CLI config JSON uses the new flat config shape.
 
+Custom attributes are configured by joining a v10 catalog with authored site policy:
+
+```ts
+import { defineCustomAttributes } from "@v-office/website-sdk";
+
+const customAttributes = defineCustomAttributes({
+  catalog,
+  select: {
+    region: {
+      label: { "de-DE": "Region", "en-US": "Region" },
+      filter: true,
+      optionLabels: {
+        north: { "de-DE": "Norden", "en-US": "North" },
+      },
+    },
+  },
+});
+```
+
+See `instructions/custom-attributes.md` before migrating an older
+`customAttributeDefinitionManifest` configuration.
+
 See `instructions/` for the full consumer documentation. Version-specific release notes and migration details live under `instructions/versions/`, with indexes at `instructions/CHANGELOG.md` and `instructions/MIGRATION.md`.

package/dist/cli.mjs

@@ -1,6 +1,6 @@
 #!/usr/bin/env node
-import { Pt as defineWebsiteSDKOptions, t as createWebsiteSDK } from "./client-45_ofP_d.mjs";
-import { SearchSearchSortSchema } from "@v-office/sdk-core";
+import { t as createWebsiteSDK, zt as defineWebsiteSDKOptions } from "./client-BNbBfJtO.mjs";
+import { SearchSearchSortSchema, defineCustomAttributesFromUnknown } from "@v-office/sdk-core";
 import { Console, Effect, FileSystem, Layer, Option, Path, Schema, Stdio, Terminal } from "effect";
 import { Command, Flag } from "effect/unstable/cli";
 import { inspect } from "node:util";
@@ -16,7 +16,7 @@ var CLICheckFailed = class extends Error {
 const toCLIError = (message, cause) => cause instanceof Error ? new CLICheckFailed(`${message}: ${cause.message}`, { cause }) : new CLICheckFailed(message, { cause });
 //#endregion
 //#region package.json
-var version = "2.7.0";
+var version = "2.8.0";
 //#endregion
 //#region src/cli/output.ts
 const toJson = (value) => Effect.try({
@@ -80,7 +80,28 @@ const WebsiteV10CLIConfigSchema = Schema.Struct({
 const WebsiteSDKCLIConfigSchema = Schema.Union([WebsiteV9CLIConfigSchema, WebsiteV10CLIConfigSchema]);
 const decodeCLIConfig = (input, path) => Schema.decodeUnknownEffect(WebsiteSDKCLIConfigSchema)(input).pipe(Effect.mapError((cause) => toCLIError(`Invalid Website SDK config file at ${path}. Expected a complete v9 or v10 config`, cause)));
 const getRequiredEnv = (name) => Effect.sync(() => process.env[name]).pipe(Effect.flatMap((value) => value === void 0 || value.trim().length === 0 ? Effect.fail(new CLICheckFailed(`Missing required environment variable ${name}.`)) : Effect.succeed(value)));
-const readOptions = (root, fallback) => Option.isSome(root.options) ? readJsonFile(root.options.value, "Website SDK options").pipe(Effect.map(defineWebsiteSDKOptions)) : Effect.succeed(fallback);
+/**
+* `customAttributes` in the options file holds the *inputs* to
+* `defineCustomAttributes` — a catalog plus product policy — not a finished
+* registry. A registry is the output of validation, so taking one verbatim from
+* JSON would mean trusting a shape nothing checked. Running the join here applies
+* every invariant to the CLI path exactly as to the TypeScript path.
+*/
+const toWebsiteSDKOptions = (input, path) => Effect.try({
+	try: () => {
+		const { customAttributes, ...rest } = input ?? {};
+		return defineWebsiteSDKOptions(customAttributes === void 0 ? rest : {
+			...rest,
+			customAttributes: defineCustomAttributesFromUnknown(customAttributes)
+		});
+	},
+	catch: (cause) => toCLIError(`Invalid Website SDK options file at ${path}`, cause)
+});
+const readOptions = (root, fallback) => {
+	if (Option.isNone(root.options)) return Effect.succeed(fallback);
+	const path = root.options.value;
+	return readJsonFile(path, "Website SDK options").pipe(Effect.flatMap((input) => toWebsiteSDKOptions(input, path)));
+};
 const fromConfigFile = (root) => {
 	if (Option.isNone(root.config)) return fromEnvironment(root);
 	const path = root.config.value;