Documentation
UnbxdSearchWrapper - SSR

UnbxdSearchWrapperSSR

Overview

The UnbxdSearchWrapperSSR is a top-level wrapper component that encapsulates all Server-Side Rendering (SSR) components or hooks used in the application. It acts as the foundational layer for the SDK's functionality, ensuring that any necessary configuration or setup is applied globally. The wrapper accepts a set of props that allow users to customize the behavior of the SDK to suit their specific needs.

Note:
The server-side rendering for this application is powered by Next.js. As of now we support only Next.js for SSR.

Usage

import { headers } from "next/headers";
import { UnbxdSearchWrapperSSR } from "@unbxd-ui/react-search-hooks";
 
const headerList = headers();
const currentPath = headerList.get("x-path-name");
 
<UnbxdSearchWrapperSSR
	siteKey="TEST_SITEKEY" 
	apiKey="TEST_APIKEY" 
	defaultValues={{ ... }}
	webUrlConfig={{
		...,
		setWebUrl: (newUrl) => { window.history.pushState({}, "", newUrl); }
	}}
	apiUrlConfig={{ ... }}
	onEvent={({type, message, value, state}) => { }}
	currentPath={currentPath}
	>
	... 
</UnbxdSearchWrapperSSR>
⚠️
Important:

The UnbxdSearchWrapperSSR component is the core of the SDK, managing all logic and data handling; all other components must be nested within this main component for the search functionality to work seamlessly.

Configuring Search vs Category

  1. Search: A page is considered a search page by default unless configured differently.
  2. Category: To designate a page as a category page, users should pass the browse configurations within the wrapper. For details on how to set this up, refer to the apiUrlConfig > category configurations.

Middlewares

To manage headers during the first render in SSR, use Middlewares. Middleware can capture headers like Authorization for authenticated requests, User-Agent for device-specific content, or Accept-Language for localization etc. The captured headers can be passed to the server-side rendering process, where the initial render will customize content based on these headers.

export function middleware(request: NextRequest) {
	const headers = new Headers(request.headers);
	headers.set("x-path-name", request.nextUrl.href);
	return NextResponse.next({ headers });
}

Props

siteKey

string
  • This is the unique Site Key assigned by Unbxd to every site created in the console dashboard.
  • Refer to this section for steps on how to get the Site Key for your account.

apiKey

string
  • This is the unique API Key assigned to every site created in the console dashboard.
  • Refer to this section for steps on how to get the API Key for your account.

defaultValues

object
  • This takes in the default values for query, pageSize, view, sort, currentPage .
ConfigDatatypeDefault value
querystring*
currentPagenumber1
pageSizenumber12
viewstring""
sortstring""
  • Usage:
defaultValues = { pageSize: 4, query: "pants", currentPage: 3, view: "", sort: "" };

webUrlConfig

object
  • Allows you to pass various settings related to the URL to make it more user-friendly. These configurations can include adjustments such as cleaner URL structures, more readable query parameters, or optimized links, enhancing the overall user experience and improving navigation clarity. Below is the usage with each config having default values.
ConfigDatatypeDefault valueDescription
hashModebooleanfalseTurn this flag on if you want the URL to use hash (#) instead of using regular query string delimiter (?).
queryParamSeperatorstring&Seperator used to seperate out each query param in the url.
keySeperatorstring=Seperator used to seperate each param key and value.
orderOfParamsarray[]Add the keys in the order you want them to appear in the url.
queryobject{ addToUrl: true, key: "query" }- addToUrl : Turn to true/false to remove query param from the url.

- key : Pass this to customize the query param key in the url.
categoryobject{ addToUrl: true, key: "p" }- addToUrl : Turn to true/false to add/remove category page info from the url.

- key : Whatever passed in here , is used as a key for the browse query param in the url.
sortobject{ addToUrl: true, key: "sort", values: {} }- addToUrl: Turn to true/false to add/remove the sort param from the url.

- key: Whatever passed in here , is used as a key for the sort in the url.

- values: This works as a replacer for the values of sort.
viewobject{ addToUrl: false, key: "view", values: {} }- addToUrl: Turn to true/false to add/remove the view (view) param from the url.

- key: Whatever passed in here , is used as a key for the view in the url.

- values: This works as a replacer for the values of view
pageSizeobject{ addToUrl: true, key: "rows" }- addToUrl: Turn to true/false to add/remove the pagesize (rows) param from the url.

- key: Whatever passed in here , is used as a key for the pagesize in the url.
paginationobject{ addToUrl: true, key: "start", usePageNo: true}- addToUrl - Turn to true/false to add/remove the page (page/start) param from the url.

- key - Whatever passed in here , is used as a key for the page in the url.

- usePageNo: Indicates whether to use page numbers (1,2,3 etc) or indices (0,12,24 etc) in the url.
facetsobject{ algo: "CUSTOM" , addToUrl: true, valuesSeparator: ",", keys: {}, values: {}}- algo: , addToUrl: When turned off , the filter string would not be added to the url.

- valuesSeparator: Pass in the character which you would like to use as a seperator between the values for same facet.

- keys: Replace the facet actual names with some custom names in the url .

- values: Replace the facet actual values with some custom values in the url .
externalParamsobjectnullThese are the params other than what unbxd appends , that user wants to add and retain in the url . This can have either of three values : null, [] , ["location", "test_param"]. (null: No external params will be considered, []: All external params other than unbxd will be considered , ["location"]: Whatever passed in here , for eg: location here will only be retained.)
rangeFacetsarray[]Mention all the range facets names that you would be using.This would help sdk to render facets better.
categoryFacetsarray[]Mention all the category facets names that you would be using.This would help sdk to render facets better.
setWebUrlfunction(newUrl: string) => { window.history.pushState({}, "", newUrl); }This function provides users with flexibility to customize how URL changes are handled in the application. Users can choose to either push new entries to the browser's history stack or replace the current entry, depending on the desired navigation behavior. Additionally, users have the option to leverage router functions to further control URL updates based on specific requirements.
  • Usage:
webUrlConfig = {
	hashMode: false
	queryParamSeperator: "&"
	keySeperator: "="
	orderOfParams: []
	query: {
		addToUrl: true,
		key: "query",
	},
	category: {
		addToUrl: true,
		key: "browse"
	}
	sort: {
		addToUrl: true,
		key: "sort",
		values: {}
	},
	view: {
		addToUrl: false,
		key: "view",
		values: {}
	},
	pageSize: {
		addToUrl: true,
		key: "rows"
	},
	pagination: {
		addToUrl: true,
		key: "start",
		usePageNo: true
	},
	facets: {
		addToUrl: true,
		valuesSeparator: ",",
		keys: {},
		values: {},
	},
	externalParams: null,
	rangeFacets: [],
	categoryFacets: [],
	setWebUrl: (newUrl) => {
		window.history.pushState({}, "", newUrl);
	}
}
  • If you are using React router below can be the code for customizing the behaviour of the url.
const navigate = useNavigate();
 
const webUrlConfig = {
	// ... other configs ...
	setWebUrl: (newUrl) => {
		navigate(newUrl);
	}
}

apiUrlConfig

object
  • This config allows you to pass some cutomization and additional features that are present to make in API URL.
ConfigDatatypeDefault valueDescription
categoryobject{browseQueryParam: 'p', page: '', page_type: '' }- browseQueryParam : parameter that will go in the api url . Values can be p or p-id.

- page: Category page path needs to be passed in here.If left empty ,page will be considered as a SEARCH page.

- page_type: Type of the category page . Value can be boolean.
productsobject{fields: []}- fields: Pass in the name of fields that needs to be extracted in the search response.

variantsobject{enabled: false, count: 5, groupBy: 'v_colour;, attributes: ["title", "v_imageUrl"], mapping: {"image_url": v_imageUrl}}- enabled: Determines whether the variants should be made available for the products or not.

- count: Refers to the number of variants that needs to be shown for a product.

- groupBy: parameter that is used to group items in a dataset based on a specific field value. It's important to note that the field name used in the groupBy parameter should match the field name in the catalogue, otherwise the grouping may not work correctly.

- attributes: List of fields you need for each variant.

-mapping: Field mapping of the catalog attributes to the variant attributes. This is needed to render the variant information correctly.

spellCheckobject{enabled: false}- enabled: This determines whether the spellcheck should be made available or not.
facetMultiSelectbooleantrueAllows a user to select multiple values within a single facet .
uc_paramstring""
extraParamsobject{}Allows to pass some extra params which are needed to be in the search api call. For the values it can be anything including function.
headersobject{}Headers is an object that takes in search api headers and passes it to the Search Api. For the User id and Device type pass it in as Unbxd-User-Id and Unbxd-Device-Type.
đź’ˇ
Note:
  • To manage headers during the first render in SSR , use Middlewares. - Middleware can capture headers like Authorization for authenticated requests, User-Agent for device-specific content, or Accept-Language for localization etc. - The captured headers can be passed to the server-side rendering process, where the initial render will customize content based on these headers.
  • Usage:
apiUrlConfig = {
	category: {
		browseQueryParam: "p",
		page: "",
		page_type: "boolean",
	},
	variants: {
		enabled: true,
		count: 6,
		groupBy: "v_colour",
		attributes: ["title", "v_imageUrl"],
		mapping: { image_url: "v_imageUrl" },
	},
	spellCheck: {
		enabled: true,
	},
	facetMultiSelect: true,
	uc_param: "",
	extraParams: { test: "abc" },
};

onEvent

function
  • A function which helps in capture events and errors. Users can further run additional pieces of code like error handling or event tracking.
  • Default Value:
const onEvent = ({ type, message, value, state }) => {
	if (message) console.log(`${type}:`, message, value);
	else console.log(type);
};
  • In parameters it receives :
    • type: Which is the type of event like BEFORE_API_CALL , AFTER_API_CALL etc.
    • message:
    • state : Current state values like current page , current selected pagesize , current query etc.
    • value:
  • Checkout the full list of events below :
ConfigDescription
INITIALISEDThis is the event triggered for the first time , once the Wrapper has initialized.
BEFORE_API_CALLThis is the event that is triggered just before the Api call initiates.
AFTER_API_CALLThis is the event that gets triggered once the api call is done.
API_ERRORThis is the event that gets triggered if the API call fails. The error details can be found in the state.error block.
QUERY_UPDATEDEvent that gets triggered when a query has been updated.
SORT_CLICKEDEvent that gets triggered on updating the sort.
BANNER_CLICKEDEvent that gets triggered when there is a click on the banner.
BREADCRUMB_CLICKEDEvent that gets triggered when there is a click on the breadcrumb.
FACET_ADDEDEvent that gets triggered once a facet has been selected.
FACET_REMOVEDEvent that gets triggered once a facet has been de-selected.
FACET_CLEAREDEvent that gets triggered once all facets has been cleared.
PAGE_SIZE_CLICKEDEvent that gets triggered when a pagesize has been selected.
PAGE_CLICKEDEvent that gets triggered when a page number (in pagination) has been selected.
PRODUCT_VIEW_CLICKEDEvent that gets triggered on selecting a view.
ERROREvent that gets triggered when an error occurs in some component.

currentPath

string
required

Send the current web url here, this helps sdk to maintain the state of the application.

  • Default Value: "".
đź’ˇ
Note:
  • To manage headers during the first render in SSR, use Middlewares. - Middleware can capture headers like Authorization for authenticated requests, User-Agent for device-specific content, or Accept-Language for localization etc. - The captured headers can be passed to the server-side rendering process, where the initial render will customize content based on these headers.