@depict-ai/ui 2.1.7 → 2.1.8

package/ES10/index.cjs

@@ -76,7 +76,7 @@ $parcel$export(module.exports, "defaultColsAtSize", () => $33eed84f447aa0c0$expo
 $parcel$export(module.exports, "defaultCategoryTitlePlugin", () => $33eed84f447aa0c0$export$7bf543b9d9be2c22);
 $parcel$export(module.exports, "version", () => $aa1938dec50d6c12$export$83d89fbfd8236492);
 /*! Depict.ai search and product listing SDK */
-const $aa1938dec50d6c12$export$83d89fbfd8236492 = "2.1.7";
+const $aa1938dec50d6c12$export$83d89fbfd8236492 = "2.1.8";
 const $a68b73fd7ba0853f$var$fallback_operator = "in";
 const $a68b73fd7ba0853f$var$fallback_token = "";
 const $a68b73fd7ba0853f$var$legacy_filter_prefix = "filter_";
@@ -420,6 +420,7 @@ function $858fdcf73148519f$var$make_srcset(url, resolutions) {
   return resolutions.map(width => "".concat($858fdcf73148519f$var$generateImageUrl(url, width), " ").concat(width, "w")).join(", ");
 }
 function $858fdcf73148519f$var$generateImageUrl(url, width) {
+  // This function is quite slow, we maybe could do string concat with encodeURIComponent instead if shopify handles double width params well?
   url.searchParams.set("width", width);
   return url.href;
 }
@@ -4206,7 +4207,13 @@ function $367b536a2a94d24e$export$e183a13865960371(params_to_default_value, rout
   const entries = Object.entries(params_to_default_value);
   const event_handler = $52FdA$depictaiutilishared.catchify((what_happened, args) => {
     // Intentionally always update our signals to the history state to allow external control of SDK state for doing things like https://linear.app/depictai/issue/X-1432/is-this-possible-with-the-depict-sdk
-    $367b536a2a94d24e$var$history_state_change(signals, entries, what_happened === "popstate" ? args.state : history.state);
+    if (what_happened !== "popstate") return;
+    // Had to undo the comment above,but leaving the history. Doing this because discovering why it doesn't work is a deja-vu and I don't want to have to discover it again.
+    // If we want others to interface with our state, it's better to expose it from DepictCategory/DepictSearch
+    // The reason for that is because writes to the state trigger writes to the state (something about local filter state, see the comment where `last_remote_state !== available_filters_()` happens in create_modified_filters.tsx)
+    // And can infinite loop, like in https://app.jiminny.com/playback/569c8f65-edea-4735-bd9e-4eb5a0b14cad
+    // It's the classical equilibrium problem when syncing state both down and up, and it's much easier to avoid than solve
+    $367b536a2a94d24e$var$history_state_change(signals, entries, args.state);
   });
   // createRenderEffect because we need the instant execution so the signals always contain values, even before solid's render phase
   $52FdA$solidjs.createRenderEffect(() => {

package/ES10/index.d.ts

@@ -7,7 +7,7 @@ import { CategorySuggestion, SearchSuggestionsResponse } from "@depict-ai/types/
 import { BaseSearchRequest } from "@depict-ai/types/api/BaseSearchRequest";
 import { SearchSuggestionsRequest } from "@depict-ai/types/api/SearchSuggestionsRequest";
 import { ProductListingRequestV2 } from "@depict-ai/types/api/ProductListingRequestV2";
-export const version = "2.1.7";
+export const version = "2.1.8";
 /**
  * Use `javascript_media_query` but return a reactive accessor instead of taking a callback function
  */

package/ES10/index.js

@@ -9,7 +9,7 @@ import { createStore as $8tj43$createStore, reconcile as $8tj43$reconcile } from
 /*! Depict.ai search and product listing SDK */
 import { register_es_version } from "../multi_import_deduplicator.mjs";
 register_es_version("ui", "ES10");
-const $8db9a15135765c11$export$83d89fbfd8236492 = "2.1.7";
+const $8db9a15135765c11$export$83d89fbfd8236492 = "2.1.8";
 const $2855bffe06ef7a03$var$fallback_operator = "in";
 const $2855bffe06ef7a03$var$fallback_token = "";
 const $2855bffe06ef7a03$var$legacy_filter_prefix = "filter_";
@@ -353,6 +353,7 @@ function $56047603f9d212b6$var$make_srcset(url, resolutions) {
   return resolutions.map(width => "".concat($56047603f9d212b6$var$generateImageUrl(url, width), " ").concat(width, "w")).join(", ");
 }
 function $56047603f9d212b6$var$generateImageUrl(url, width) {
+  // This function is quite slow, we maybe could do string concat with encodeURIComponent instead if shopify handles double width params well?
   url.searchParams.set("width", width);
   return url.href;
 }
@@ -4139,7 +4140,13 @@ function $972f6bce0f9d61be$export$e183a13865960371(params_to_default_value, rout
   const entries = Object.entries(params_to_default_value);
   const event_handler = $8tj43$catchify((what_happened, args) => {
     // Intentionally always update our signals to the history state to allow external control of SDK state for doing things like https://linear.app/depictai/issue/X-1432/is-this-possible-with-the-depict-sdk
-    $972f6bce0f9d61be$var$history_state_change(signals, entries, what_happened === "popstate" ? args.state : history.state);
+    if (what_happened !== "popstate") return;
+    // Had to undo the comment above,but leaving the history. Doing this because discovering why it doesn't work is a deja-vu and I don't want to have to discover it again.
+    // If we want others to interface with our state, it's better to expose it from DepictCategory/DepictSearch
+    // The reason for that is because writes to the state trigger writes to the state (something about local filter state, see the comment where `last_remote_state !== available_filters_()` happens in create_modified_filters.tsx)
+    // And can infinite loop, like in https://app.jiminny.com/playback/569c8f65-edea-4735-bd9e-4eb5a0b14cad
+    // It's the classical equilibrium problem when syncing state both down and up, and it's much easier to avoid than solve
+    $972f6bce0f9d61be$var$history_state_change(signals, entries, args.state);
   });
   // createRenderEffect because we need the instant execution so the signals always contain values, even before solid's render phase
   $8tj43$createRenderEffect(() => {

package/latest/index.cjs

@@ -70,7 +70,7 @@ $parcel$export(module.exports, "defaultColsAtSize", () => $a3280f0aad997933$expo
 $parcel$export(module.exports, "defaultCategoryTitlePlugin", () => $a3280f0aad997933$export$7bf543b9d9be2c22);
 $parcel$export(module.exports, "version", () => $b757f75811f3261f$export$83d89fbfd8236492);
 /*! Depict.ai search and product listing SDK */
-const $b757f75811f3261f$export$83d89fbfd8236492 = "2.1.7";
+const $b757f75811f3261f$export$83d89fbfd8236492 = "2.1.8";
 const $1ab22f2cd39b3061$var$fallback_operator = "in";
 const $1ab22f2cd39b3061$var$fallback_token = "";
 const $1ab22f2cd39b3061$var$legacy_filter_prefix = "filter_";
@@ -406,6 +406,7 @@ function $19950faaac026e09$var$make_srcset(url, resolutions) {
   return resolutions.map(width => `${$19950faaac026e09$var$generateImageUrl(url, width)} ${width}w`).join(", ");
 }
 function $19950faaac026e09$var$generateImageUrl(url, width) {
+  // This function is quite slow, we maybe could do string concat with encodeURIComponent instead if shopify handles double width params well?
   url.searchParams.set("width", width);
   return url.href;
 }
@@ -3952,7 +3953,13 @@ function $6e22b5314fb52f4c$export$e183a13865960371(params_to_default_value, rout
   const entries = Object.entries(params_to_default_value);
   const event_handler = $gVhhF$depictaiutilishared.catchify((what_happened, args) => {
     // Intentionally always update our signals to the history state to allow external control of SDK state for doing things like https://linear.app/depictai/issue/X-1432/is-this-possible-with-the-depict-sdk
-    $6e22b5314fb52f4c$var$history_state_change(signals, entries, what_happened === "popstate" ? args.state : history.state);
+    if (what_happened !== "popstate") return;
+    // Had to undo the comment above,but leaving the history. Doing this because discovering why it doesn't work is a deja-vu and I don't want to have to discover it again.
+    // If we want others to interface with our state, it's better to expose it from DepictCategory/DepictSearch
+    // The reason for that is because writes to the state trigger writes to the state (something about local filter state, see the comment where `last_remote_state !== available_filters_()` happens in create_modified_filters.tsx)
+    // And can infinite loop, like in https://app.jiminny.com/playback/569c8f65-edea-4735-bd9e-4eb5a0b14cad
+    // It's the classical equilibrium problem when syncing state both down and up, and it's much easier to avoid than solve
+    $6e22b5314fb52f4c$var$history_state_change(signals, entries, args.state);
   });
   // createRenderEffect because we need the instant execution so the signals always contain values, even before solid's render phase
   $gVhhF$solidjs.createRenderEffect(() => {

package/latest/index.d.ts

@@ -7,7 +7,7 @@ import { CategorySuggestion, SearchSuggestionsResponse } from "@depict-ai/types/
 import { BaseSearchRequest } from "@depict-ai/types/api/BaseSearchRequest";
 import { SearchSuggestionsRequest } from "@depict-ai/types/api/SearchSuggestionsRequest";
 import { ProductListingRequestV2 } from "@depict-ai/types/api/ProductListingRequestV2";
-export const version = "2.1.7";
+export const version = "2.1.8";
 /**
  * Use `javascript_media_query` but return a reactive accessor instead of taking a callback function
  */

package/latest/index.js

@@ -6,7 +6,7 @@ import { createStore as $9HbP8$createStore, reconcile as $9HbP8$reconcile } from
 /*! Depict.ai search and product listing SDK */
 import { register_es_version } from "../multi_import_deduplicator.mjs";
 register_es_version("ui", "latest");
-const $ec291e0010116877$export$83d89fbfd8236492 = "2.1.7";
+const $ec291e0010116877$export$83d89fbfd8236492 = "2.1.8";
 const $4147651646da990a$var$fallback_operator = "in";
 const $4147651646da990a$var$fallback_token = "";
 const $4147651646da990a$var$legacy_filter_prefix = "filter_";
@@ -342,6 +342,7 @@ function $e8ffe11ed01df0fe$var$make_srcset(url, resolutions) {
   return resolutions.map(width => `${$e8ffe11ed01df0fe$var$generateImageUrl(url, width)} ${width}w`).join(", ");
 }
 function $e8ffe11ed01df0fe$var$generateImageUrl(url, width) {
+  // This function is quite slow, we maybe could do string concat with encodeURIComponent instead if shopify handles double width params well?
   url.searchParams.set("width", width);
   return url.href;
 }
@@ -3888,7 +3889,13 @@ function $ca6f574bd8772184$export$e183a13865960371(params_to_default_value, rout
   const entries = Object.entries(params_to_default_value);
   const event_handler = $9HbP8$catchify((what_happened, args) => {
     // Intentionally always update our signals to the history state to allow external control of SDK state for doing things like https://linear.app/depictai/issue/X-1432/is-this-possible-with-the-depict-sdk
-    $ca6f574bd8772184$var$history_state_change(signals, entries, what_happened === "popstate" ? args.state : history.state);
+    if (what_happened !== "popstate") return;
+    // Had to undo the comment above,but leaving the history. Doing this because discovering why it doesn't work is a deja-vu and I don't want to have to discover it again.
+    // If we want others to interface with our state, it's better to expose it from DepictCategory/DepictSearch
+    // The reason for that is because writes to the state trigger writes to the state (something about local filter state, see the comment where `last_remote_state !== available_filters_()` happens in create_modified_filters.tsx)
+    // And can infinite loop, like in https://app.jiminny.com/playback/569c8f65-edea-4735-bd9e-4eb5a0b14cad
+    // It's the classical equilibrium problem when syncing state both down and up, and it's much easier to avoid than solve
+    $ca6f574bd8772184$var$history_state_change(signals, entries, args.state);
   });
   // createRenderEffect because we need the instant execution so the signals always contain values, even before solid's render phase
   $9HbP8$createRenderEffect(() => {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@depict-ai/ui",
-  "version": "2.1.7",
+  "version": "2.1.8",
   "description": "Base package containing the actual UI of Depict UI along with translations, with a not-simplified API. We recommend using @depict-ai/js-ui or @depict-ai/react-ui instead.",
   "packageManager": "yarn@3.2.2",
   "sass": "styles.scss",

package/server/ES10/index.cjs

@@ -76,7 +76,7 @@ $parcel$export(module.exports, "defaultColsAtSize", () => $33eed84f447aa0c0$expo
 $parcel$export(module.exports, "defaultCategoryTitlePlugin", () => $33eed84f447aa0c0$export$7bf543b9d9be2c22);
 $parcel$export(module.exports, "version", () => $aa1938dec50d6c12$export$83d89fbfd8236492);
 /*! Depict.ai search and product listing SDK */
-const $aa1938dec50d6c12$export$83d89fbfd8236492 = "2.1.7";
+const $aa1938dec50d6c12$export$83d89fbfd8236492 = "2.1.8";
 const $a68b73fd7ba0853f$var$fallback_operator = "in";
 const $a68b73fd7ba0853f$var$fallback_token = "";
 const $a68b73fd7ba0853f$var$legacy_filter_prefix = "filter_";
@@ -416,6 +416,7 @@ function $858fdcf73148519f$var$make_srcset(url, resolutions) {
   return resolutions.map(width => "".concat($858fdcf73148519f$var$generateImageUrl(url, width), " ").concat(width, "w")).join(", ");
 }
 function $858fdcf73148519f$var$generateImageUrl(url, width) {
+  // This function is quite slow, we maybe could do string concat with encodeURIComponent instead if shopify handles double width params well?
   url.searchParams.set("width", width);
   return url.href;
 }
@@ -3336,7 +3337,13 @@ function $367b536a2a94d24e$export$e183a13865960371(params_to_default_value, rout
   const entries = Object.entries(params_to_default_value);
   const event_handler = $3hooq$depictaiutilishared.catchify((what_happened, args) => {
     // Intentionally always update our signals to the history state to allow external control of SDK state for doing things like https://linear.app/depictai/issue/X-1432/is-this-possible-with-the-depict-sdk
-    $367b536a2a94d24e$var$history_state_change(signals, entries, what_happened === "popstate" ? args.state : history.state);
+    if (what_happened !== "popstate") return;
+    // Had to undo the comment above,but leaving the history. Doing this because discovering why it doesn't work is a deja-vu and I don't want to have to discover it again.
+    // If we want others to interface with our state, it's better to expose it from DepictCategory/DepictSearch
+    // The reason for that is because writes to the state trigger writes to the state (something about local filter state, see the comment where `last_remote_state !== available_filters_()` happens in create_modified_filters.tsx)
+    // And can infinite loop, like in https://app.jiminny.com/playback/569c8f65-edea-4735-bd9e-4eb5a0b14cad
+    // It's the classical equilibrium problem when syncing state both down and up, and it's much easier to avoid than solve
+    $367b536a2a94d24e$var$history_state_change(signals, entries, args.state);
   });
   // createRenderEffect because we need the instant execution so the signals always contain values, even before solid's render phase
   $3hooq$solidjs.createRenderEffect(() => {

package/server/ES10/index.d.ts

@@ -7,7 +7,7 @@ import { CategorySuggestion, SearchSuggestionsResponse } from "@depict-ai/types/
 import { BaseSearchRequest } from "@depict-ai/types/api/BaseSearchRequest";
 import { SearchSuggestionsRequest } from "@depict-ai/types/api/SearchSuggestionsRequest";
 import { ProductListingRequestV2 } from "@depict-ai/types/api/ProductListingRequestV2";
-export const version = "2.1.7";
+export const version = "2.1.8";
 /**
  * Use `javascript_media_query` but return a reactive accessor instead of taking a callback function
  */

package/server/ES10/index.js

@@ -9,7 +9,7 @@ import { createStore as $b8hua$createStore, reconcile as $b8hua$reconcile } from
 /*! Depict.ai search and product listing SDK */
 import { register_es_version } from "../../multi_import_deduplicator.mjs";
 register_es_version("ui", "ES10");
-const $8db9a15135765c11$export$83d89fbfd8236492 = "2.1.7";
+const $8db9a15135765c11$export$83d89fbfd8236492 = "2.1.8";
 const $2855bffe06ef7a03$var$fallback_operator = "in";
 const $2855bffe06ef7a03$var$fallback_token = "";
 const $2855bffe06ef7a03$var$legacy_filter_prefix = "filter_";
@@ -349,6 +349,7 @@ function $56047603f9d212b6$var$make_srcset(url, resolutions) {
   return resolutions.map(width => "".concat($56047603f9d212b6$var$generateImageUrl(url, width), " ").concat(width, "w")).join(", ");
 }
 function $56047603f9d212b6$var$generateImageUrl(url, width) {
+  // This function is quite slow, we maybe could do string concat with encodeURIComponent instead if shopify handles double width params well?
   url.searchParams.set("width", width);
   return url.href;
 }
@@ -3269,7 +3270,13 @@ function $972f6bce0f9d61be$export$e183a13865960371(params_to_default_value, rout
   const entries = Object.entries(params_to_default_value);
   const event_handler = $b8hua$catchify((what_happened, args) => {
     // Intentionally always update our signals to the history state to allow external control of SDK state for doing things like https://linear.app/depictai/issue/X-1432/is-this-possible-with-the-depict-sdk
-    $972f6bce0f9d61be$var$history_state_change(signals, entries, what_happened === "popstate" ? args.state : history.state);
+    if (what_happened !== "popstate") return;
+    // Had to undo the comment above,but leaving the history. Doing this because discovering why it doesn't work is a deja-vu and I don't want to have to discover it again.
+    // If we want others to interface with our state, it's better to expose it from DepictCategory/DepictSearch
+    // The reason for that is because writes to the state trigger writes to the state (something about local filter state, see the comment where `last_remote_state !== available_filters_()` happens in create_modified_filters.tsx)
+    // And can infinite loop, like in https://app.jiminny.com/playback/569c8f65-edea-4735-bd9e-4eb5a0b14cad
+    // It's the classical equilibrium problem when syncing state both down and up, and it's much easier to avoid than solve
+    $972f6bce0f9d61be$var$history_state_change(signals, entries, args.state);
   });
   // createRenderEffect because we need the instant execution so the signals always contain values, even before solid's render phase
   $b8hua$createRenderEffect(() => {

package/server/latest/index.cjs

@@ -70,7 +70,7 @@ $parcel$export(module.exports, "defaultColsAtSize", () => $a3280f0aad997933$expo
 $parcel$export(module.exports, "defaultCategoryTitlePlugin", () => $a3280f0aad997933$export$7bf543b9d9be2c22);
 $parcel$export(module.exports, "version", () => $b757f75811f3261f$export$83d89fbfd8236492);
 /*! Depict.ai search and product listing SDK */
-const $b757f75811f3261f$export$83d89fbfd8236492 = "2.1.7";
+const $b757f75811f3261f$export$83d89fbfd8236492 = "2.1.8";
 const $1ab22f2cd39b3061$var$fallback_operator = "in";
 const $1ab22f2cd39b3061$var$fallback_token = "";
 const $1ab22f2cd39b3061$var$legacy_filter_prefix = "filter_";
@@ -402,6 +402,7 @@ function $19950faaac026e09$var$make_srcset(url, resolutions) {
   return resolutions.map(width => `${$19950faaac026e09$var$generateImageUrl(url, width)} ${width}w`).join(", ");
 }
 function $19950faaac026e09$var$generateImageUrl(url, width) {
+  // This function is quite slow, we maybe could do string concat with encodeURIComponent instead if shopify handles double width params well?
   url.searchParams.set("width", width);
   return url.href;
 }
@@ -3119,7 +3120,13 @@ function $6e22b5314fb52f4c$export$e183a13865960371(params_to_default_value, rout
   const entries = Object.entries(params_to_default_value);
   const event_handler = $5vyXB$depictaiutilishared.catchify((what_happened, args) => {
     // Intentionally always update our signals to the history state to allow external control of SDK state for doing things like https://linear.app/depictai/issue/X-1432/is-this-possible-with-the-depict-sdk
-    $6e22b5314fb52f4c$var$history_state_change(signals, entries, what_happened === "popstate" ? args.state : history.state);
+    if (what_happened !== "popstate") return;
+    // Had to undo the comment above,but leaving the history. Doing this because discovering why it doesn't work is a deja-vu and I don't want to have to discover it again.
+    // If we want others to interface with our state, it's better to expose it from DepictCategory/DepictSearch
+    // The reason for that is because writes to the state trigger writes to the state (something about local filter state, see the comment where `last_remote_state !== available_filters_()` happens in create_modified_filters.tsx)
+    // And can infinite loop, like in https://app.jiminny.com/playback/569c8f65-edea-4735-bd9e-4eb5a0b14cad
+    // It's the classical equilibrium problem when syncing state both down and up, and it's much easier to avoid than solve
+    $6e22b5314fb52f4c$var$history_state_change(signals, entries, args.state);
   });
   // createRenderEffect because we need the instant execution so the signals always contain values, even before solid's render phase
   $5vyXB$solidjs.createRenderEffect(() => {

package/server/latest/index.d.ts

@@ -7,7 +7,7 @@ import { CategorySuggestion, SearchSuggestionsResponse } from "@depict-ai/types/
 import { BaseSearchRequest } from "@depict-ai/types/api/BaseSearchRequest";
 import { SearchSuggestionsRequest } from "@depict-ai/types/api/SearchSuggestionsRequest";
 import { ProductListingRequestV2 } from "@depict-ai/types/api/ProductListingRequestV2";
-export const version = "2.1.7";
+export const version = "2.1.8";
 /**
  * Use `javascript_media_query` but return a reactive accessor instead of taking a callback function
  */

package/server/latest/index.js

@@ -6,7 +6,7 @@ import { createStore as $i7OB2$createStore, reconcile as $i7OB2$reconcile } from
 /*! Depict.ai search and product listing SDK */
 import { register_es_version } from "../../multi_import_deduplicator.mjs";
 register_es_version("ui", "latest");
-const $ec291e0010116877$export$83d89fbfd8236492 = "2.1.7";
+const $ec291e0010116877$export$83d89fbfd8236492 = "2.1.8";
 const $4147651646da990a$var$fallback_operator = "in";
 const $4147651646da990a$var$fallback_token = "";
 const $4147651646da990a$var$legacy_filter_prefix = "filter_";
@@ -338,6 +338,7 @@ function $e8ffe11ed01df0fe$var$make_srcset(url, resolutions) {
   return resolutions.map(width => `${$e8ffe11ed01df0fe$var$generateImageUrl(url, width)} ${width}w`).join(", ");
 }
 function $e8ffe11ed01df0fe$var$generateImageUrl(url, width) {
+  // This function is quite slow, we maybe could do string concat with encodeURIComponent instead if shopify handles double width params well?
   url.searchParams.set("width", width);
   return url.href;
 }
@@ -3055,7 +3056,13 @@ function $ca6f574bd8772184$export$e183a13865960371(params_to_default_value, rout
   const entries = Object.entries(params_to_default_value);
   const event_handler = $i7OB2$catchify((what_happened, args) => {
     // Intentionally always update our signals to the history state to allow external control of SDK state for doing things like https://linear.app/depictai/issue/X-1432/is-this-possible-with-the-depict-sdk
-    $ca6f574bd8772184$var$history_state_change(signals, entries, what_happened === "popstate" ? args.state : history.state);
+    if (what_happened !== "popstate") return;
+    // Had to undo the comment above,but leaving the history. Doing this because discovering why it doesn't work is a deja-vu and I don't want to have to discover it again.
+    // If we want others to interface with our state, it's better to expose it from DepictCategory/DepictSearch
+    // The reason for that is because writes to the state trigger writes to the state (something about local filter state, see the comment where `last_remote_state !== available_filters_()` happens in create_modified_filters.tsx)
+    // And can infinite loop, like in https://app.jiminny.com/playback/569c8f65-edea-4735-bd9e-4eb5a0b14cad
+    // It's the classical equilibrium problem when syncing state both down and up, and it's much easier to avoid than solve
+    $ca6f574bd8772184$var$history_state_change(signals, entries, args.state);
   });
   // createRenderEffect because we need the instant execution so the signals always contain values, even before solid's render phase
   $i7OB2$createRenderEffect(() => {