diff --git a/usage/sync-rules/advanced-topics/client-parameters.mdx b/usage/sync-rules/advanced-topics/client-parameters.mdx index 1c9c4e51..a012ba97 100644 --- a/usage/sync-rules/advanced-topics/client-parameters.mdx +++ b/usage/sync-rules/advanced-topics/client-parameters.mdx @@ -13,6 +13,12 @@ PowerSync already supports using **token parameters** in parameter queries. An e **Client parameters** are specified directly by the client (i.e. not through the JWT authentication token). The advantage of client parameters is that they give client-side control over what data to sync, and can therefore be used to further filter or limit synced data. A common use case is [lazy-loading](/usage/use-case-examples/infinite-scrolling#2-control-data-sync-using-client-parameters), where data is split into pages and a client parameter can be used to specify which page(s) to sync to a user, and this can update dynamically as the user paginates (or reaches the end of an infinite-scrolling feed). + + [Sync Streams](/usage/sync-streams) make it easier to use client parameters, especially for apps where parameters are managed across different UI components and tabs. + + For new apps that require client parameters, we recommend using [Sync Streams](/usage/sync-streams) (Early Alpha). + + ### Usage Client parameters are defined when [instantiating the PowerSync database](/installation/client-side-setup/instantiate-powersync-database), within the options of PowerSync's `connect()` method: