From f136d32885fc09dc838b7b88687e693a36d592bf Mon Sep 17 00:00:00 2001 From: Daniel Szoke <7881302+szokeasaurusrex@users.noreply.github.com> Date: Thu, 2 Apr 2026 15:41:12 +0200 Subject: [PATCH 1/2] docs: Update logic placement guidelines in API architecture --- .../sdk/getting-started/standards/api-architecture.mdx | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/develop-docs/sdk/getting-started/standards/api-architecture.mdx b/develop-docs/sdk/getting-started/standards/api-architecture.mdx index f05c01293f443..d86c00f5e8e04 100644 --- a/develop-docs/sdk/getting-started/standards/api-architecture.mdx +++ b/develop-docs/sdk/getting-started/standards/api-architecture.mdx @@ -24,12 +24,12 @@ These standards guide how SDKs are designed and evolved. The core philosophy: pr When deciding where new logic should live, default to server-side (Relay). Processing data in Relay keeps behavior consistent across SDK versions and avoids duplicating logic in clients that may remain deployed indefinitely. -Put logic in the SDK only when it genuinely needs to run client-side: +Logic **SHOULD** only be placed in the SDK only when it genuinely needs to run client-side, for example, if: -- It **MUST** run before data leaves the customer's application (e.g., user-controlled filtering like `before_send_*`) +- It needs to run before data leaves the customer's application (e.g., user-controlled filtering like `before_send_*`) - It requires access to platform-specific APIs - It's strictly latency-sensitive -- It **MUST** function in offline scenarios +- It needs to function in offline scenarios If data has already been collected, transform it in Relay. From fd670535df2261a0d39fde4361e38e37f7285f12 Mon Sep 17 00:00:00 2001 From: Daniel Szoke <7881302+szokeasaurusrex@users.noreply.github.com> Date: Thu, 2 Apr 2026 15:45:13 +0200 Subject: [PATCH 2/2] remove unrelated change --- develop-docs/sdk/getting-started/standards/api-architecture.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/develop-docs/sdk/getting-started/standards/api-architecture.mdx b/develop-docs/sdk/getting-started/standards/api-architecture.mdx index d86c00f5e8e04..98d0106dc2986 100644 --- a/develop-docs/sdk/getting-started/standards/api-architecture.mdx +++ b/develop-docs/sdk/getting-started/standards/api-architecture.mdx @@ -24,7 +24,7 @@ These standards guide how SDKs are designed and evolved. The core philosophy: pr When deciding where new logic should live, default to server-side (Relay). Processing data in Relay keeps behavior consistent across SDK versions and avoids duplicating logic in clients that may remain deployed indefinitely. -Logic **SHOULD** only be placed in the SDK only when it genuinely needs to run client-side, for example, if: +Put logic in the SDK only when it genuinely needs to run client-side: - It needs to run before data leaves the customer's application (e.g., user-controlled filtering like `before_send_*`) - It requires access to platform-specific APIs