@burdenoff/microfe-devportal 2026.1107.1 → 2026.1107.2

package/dist/devportal/constants/appCategories.d.ts

@@ -0,0 +1,26 @@
+/**
+ * Application categories offered by the developer portal.
+ *
+ * These are the canonical FluidGrids store categories, so an app maps onto
+ * the store's browse panel. Every form that sets an application's category
+ * (the setup wizard, Create Application and Edit Application) must use this
+ * one list: when the setup wizard used its own list, an app created there
+ * opened in Edit Application with an empty, required Category field, and the
+ * developer had to replace the category just to change visibility
+ * (BOFF-10636).
+ */
+export interface AppCategoryOption {
+    value: string;
+    label: string;
+}
+export declare const APP_CATEGORY_OPTIONS: readonly AppCategoryOption[];
+/**
+ * Category options for a form editing an existing application.
+ *
+ * Apps created before the categories were aligned can still carry an older
+ * value (for example "productivity"). That value is kept as a selectable
+ * option so opening the edit form neither blanks the field nor silently
+ * changes the app's category on save.
+ */
+export declare function appCategoryOptionsFor(currentCategory: string | null | undefined): AppCategoryOption[];
+//# sourceMappingURL=appCategories.d.ts.map

package/dist/devportal/constants/appCategories.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"appCategories.d.ts","sourceRoot":"","sources":["../../../src/devportal/constants/appCategories.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;GAUG;AAEH,MAAM,WAAW,iBAAiB;IAChC,KAAK,EAAE,MAAM,CAAC;IACd,KAAK,EAAE,MAAM,CAAC;CACf;AAED,eAAO,MAAM,oBAAoB,EAAE,SAAS,iBAAiB,EAQ5D,CAAC;AAEF;;;;;;;GAOG;AACH,wBAAgB,qBAAqB,CACnC,eAAe,EAAE,MAAM,GAAG,IAAI,GAAG,SAAS,GACzC,iBAAiB,EAAE,CAOrB"}

package/dist/devportal/constants/appCategories.js

@@ -0,0 +1,45 @@
+//#region src/devportal/constants/appCategories.ts
+var e = [
+	{
+		value: "ai",
+		label: "AI & Automation"
+	},
+	{
+		value: "integration",
+		label: "Action in an App"
+	},
+	{
+		value: "data",
+		label: "Data & Transform"
+	},
+	{
+		value: "flow",
+		label: "Flow & Logic"
+	},
+	{
+		value: "core",
+		label: "Core"
+	},
+	{
+		value: "communication",
+		label: "Communication"
+	},
+	{
+		value: "trigger",
+		label: "Triggers"
+	}
+];
+function t(t) {
+	let r = [...e], i = t?.trim();
+	return i && !r.some((e) => e.value === i) && r.push({
+		value: i,
+		label: n(i)
+	}), r;
+}
+function n(e) {
+	return e.split(/[-_\s]+/).filter(Boolean).map((e) => e.charAt(0).toUpperCase() + e.slice(1)).join(" ");
+}
+//#endregion
+export { e as APP_CATEGORY_OPTIONS, t as appCategoryOptionsFor };
+
+//# sourceMappingURL=appCategories.js.map

package/dist/devportal/constants/appCategories.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"appCategories.js","names":[],"sources":["../../../src/devportal/constants/appCategories.ts"],"sourcesContent":["/**\n * Application categories offered by the developer portal.\n *\n * These are the canonical FluidGrids store categories, so an app maps onto\n * the store's browse panel. Every form that sets an application's category\n * (the setup wizard, Create Application and Edit Application) must use this\n * one list: when the setup wizard used its own list, an app created there\n * opened in Edit Application with an empty, required Category field, and the\n * developer had to replace the category just to change visibility\n * (BOFF-10636).\n */\n\nexport interface AppCategoryOption {\n  value: string;\n  label: string;\n}\n\nexport const APP_CATEGORY_OPTIONS: readonly AppCategoryOption[] = [\n  { value: \"ai\", label: \"AI & Automation\" },\n  { value: \"integration\", label: \"Action in an App\" },\n  { value: \"data\", label: \"Data & Transform\" },\n  { value: \"flow\", label: \"Flow & Logic\" },\n  { value: \"core\", label: \"Core\" },\n  { value: \"communication\", label: \"Communication\" },\n  { value: \"trigger\", label: \"Triggers\" },\n];\n\n/**\n * Category options for a form editing an existing application.\n *\n * Apps created before the categories were aligned can still carry an older\n * value (for example \"productivity\"). That value is kept as a selectable\n * option so opening the edit form neither blanks the field nor silently\n * changes the app's category on save.\n */\nexport function appCategoryOptionsFor(\n  currentCategory: string | null | undefined,\n): AppCategoryOption[] {\n  const options = [...APP_CATEGORY_OPTIONS];\n  const current = currentCategory?.trim();\n  if (current && !options.some((option) => option.value === current)) {\n    options.push({ value: current, label: humanizeCategory(current) });\n  }\n  return options;\n}\n\nfunction humanizeCategory(value: string): string {\n  return value\n    .split(/[-_\\s]+/)\n    .filter(Boolean)\n    .map((word) => word.charAt(0).toUpperCase() + word.slice(1))\n    .join(\" \");\n}\n"],"mappings":";AAiBA,IAAa,IAAqD;CAChE;EAAE,OAAO;EAAM,OAAO;EAAmB;CACzC;EAAE,OAAO;EAAe,OAAO;EAAoB;CACnD;EAAE,OAAO;EAAQ,OAAO;EAAoB;CAC5C;EAAE,OAAO;EAAQ,OAAO;EAAgB;CACxC;EAAE,OAAO;EAAQ,OAAO;EAAQ;CAChC;EAAE,OAAO;EAAiB,OAAO;EAAiB;CAClD;EAAE,OAAO;EAAW,OAAO;EAAY;CACxC;AAUD,SAAgB,EACd,GACqB;CACrB,IAAM,IAAU,CAAC,GAAG,EAAqB,EACnC,IAAU,GAAiB,MAAM;AAIvC,QAHI,KAAW,CAAC,EAAQ,MAAM,MAAW,EAAO,UAAU,EAAQ,IAChE,EAAQ,KAAK;EAAE,OAAO;EAAS,OAAO,EAAiB,EAAQ;EAAE,CAAC,EAE7D;;AAGT,SAAS,EAAiB,GAAuB;AAC/C,QAAO,EACJ,MAAM,UAAU,CAChB,OAAO,QAAQ,CACf,KAAK,MAAS,EAAK,OAAO,EAAE,CAAC,aAAa,GAAG,EAAK,MAAM,EAAE,CAAC,CAC3D,KAAK,IAAI"}

package/dist/devportal/pages/ApplicationDetailPage.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"ApplicationDetailPage.d.ts","sourceRoot":"","sources":["../../../src/devportal/pages/ApplicationDetailPage.tsx"],"names":[],"mappings":"AAAA,OAAO,KAAK,EAAE,EAAE,EAAE,MAAM,OAAO,CAAC;AAiUhC;;GAEG;AACH,eAAO,MAAM,qBAAqB,EAAE,EAigCnC,CAAC"}
+{"version":3,"file":"ApplicationDetailPage.d.ts","sourceRoot":"","sources":["../../../src/devportal/pages/ApplicationDetailPage.tsx"],"names":[],"mappings":"AAAA,OAAO,KAAK,EAAE,EAAE,EAAE,MAAM,OAAO,CAAC;AAkUhC;;GAEG;AACH,eAAO,MAAM,qBAAqB,EAAE,EAigCnC,CAAC"}