chore(KNO-11486): exclude metadata when refetching feed after new message received

[mattmikolay]

Description

This PR updates the client SDK so that:

• The feed client supports the exclude option, used to exclude specified fields from the list feed items response payload
• When a new socket event of type "new-message" is received, the request we make to the list feed items endpoint automatically excludes the meta field from its response. meta contains the badge counts, which are already present on the socket event payload, so querying for meta is redundant.

Todos

• Merge knocklabs/switchboard#5467
• Merge knocklabs/switchboard#5478

Checklist

• Tests have been added for new features or major refactors to existing features.

Loom demo

https://www.loom.com/share/56c2bb427c31485ea8b837c3c416be04

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
javascript-ms-teams-connect-example	Ready	Preview, Comment	Feb 5, 2026 10:53pm
javascript-nextjs-example	Ready	Preview, Comment	Feb 5, 2026 10:53pm
javascript-slack-connect-example	Ready	Preview, Comment	Feb 5, 2026 10:53pm
javascript-slack-kit-example	Ready	Preview, Comment	Feb 5, 2026 10:53pm

[linear]

KNO-11486 [SDKs] Update JS SDKs to exclude badge count when refetching feed items

[changeset-bot]

🦋 Changeset detected

Latest commit: f71b7c7

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 13 packages

Name	Type
@knocklabs/client	Minor
client-example	Patch
guide-example	Patch
@knocklabs/expo	Patch
@knocklabs/react-core	Patch
@knocklabs/react-native	Patch
@knocklabs/react	Patch
@knocklabs/expo-example	Patch
ms-teams-connect-example	Patch
nextjs-app-dir-example	Patch
nextjs-example	Patch
slack-connect-example	Patch
slack-kit-example	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[mattmikolay]

Warning

This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

• chore(KNO-11486): exclude metadata when refetching feed after new message received #853 👈 (View in Graphite)
• feat(KNO-11394): initialize feed clients in compact mode by default #851
• main

This stack of pull requests is managed by Graphite. Learn more about stacking.

[mattmikolay]

@cursor review

[mattmikolay]

@cursor review

[cursor]

✅ Bugbot reviewed your changes and found no new issues!

Comment @cursor review or bugbot run to trigger another review on this PR

[thomaswhyyou]

Is it okay we are not using mergedOptions here? i.e. we don't include options.

[mattmikolay]

Good catch. This was working because the destructure of ...mergeDateRangeParams(options) accomplishes the same thing. But I think it’s better if we use mergedOptions everywhere, so I made that change.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 68.58%. Comparing base (db04746) to head (f71b7c7).
✅ All tests successful. No failed tests found.

Additional details and impacted files

@@                                 Coverage Diff                                  @@
##           mattmik-kno-11394-support-compact-mode-for-feeds     #853      +/-   ##
====================================================================================
+ Coverage                                             68.45%   68.58%   +0.12%     
====================================================================================
  Files                                                   193      193              
  Lines                                                  8062     8088      +26     
  Branches                                               1065     1076      +11     
====================================================================================
+ Hits                                                   5519     5547      +28     
+ Misses                                                 2518     2516       -2     
  Partials                                                 25       25              

Files with missing lines	Coverage Δ
packages/client/src/clients/feed/feed.ts	82.47% <100.00%> (+0.65%)	⬆️
packages/client/src/clients/feed/store.ts	100.00% <100.00%> (ø)
packages/client/src/clients/feed/utils.ts	100.00% <100.00%> (ø)

[thomaswhyyou]

Did we mean to add these?

[mattmikolay]

Yes, it’s a mistake that they weren’t already in the FetchFeedOptionsForRequest type.

FetchFeedOptionsForRequest is meant to represent the params included in the API request. Notice that the mergeDateRangeParams function transforms the inserted_at_date_range option on FeedClientOptions into the appropriate date params, e.g. inserted_at.gte, inserted_at.lte, etc.

javascript/packages/client/src/clients/feed/utils.ts

Lines 25 to 50 in 9313398

	export function mergeDateRangeParams(options: FeedClientOptions) {
	const { inserted_at_date_range, ...rest } = options;
	if (!inserted_at_date_range) {
	return rest;
	}
	const dateRangeParams: Record<string, string> = {};
	// Determine which operators to use based on the inclusive flag
	const isInclusive = inserted_at_date_range.inclusive ?? false;
	// For start date: use gte if inclusive, gt if not
	if (inserted_at_date_range.start) {
	const startOperator = isInclusive ? "inserted_at.gte" : "inserted_at.gt";
	dateRangeParams[startOperator] = inserted_at_date_range.start;
	}
	// For end date: use lte if inclusive, lt if not
	if (inserted_at_date_range.end) {
	const endOperator = isInclusive ? "inserted_at.lte" : "inserted_at.lt";
	dateRangeParams[endOperator] = inserted_at_date_range.end;
	}
	return { ...rest, ...dateRangeParams };
	}