Skip to content

fix: add missing app config fields to AppSettingsAPIResponse - #1854

Merged
oliverlaz merged 1 commit into
masterfrom
fix/app-config-response-type-drift
Sep 7, 2026
Merged

fix: add missing app config fields to AppSettingsAPIResponse#1854
oliverlaz merged 1 commit into
masterfrom
fix/app-config-response-type-drift

Conversation

@oliverlaz

Copy link
Copy Markdown
Member

Summary

The scheduled type-check job (https://github.com/GetStream/stream-chat-js/actions/runs/34104186289) failed because the live GetApp response now includes fields that AppSettingsAPIResponse.app doesn't declare, most visibly moderation_keyframe_video_enabled.
Cross-checked the full AppResponseFields schema in the server-side OpenAPI spec against src/types.ts and found 8 fields missing in total, so all of them are added here to avoid repeat failures on the next scheduled run: activity_metrics_config, chat_primary_use_case, member_custom_on_mentioned_users_enabled, member_custom_on_messages_enabled, member_custom_on_typing_events_enabled, moderation_keyframe_video_enabled, moderation_s3_image_access_role_arn, video_primary_use_case.

Test plan

  • yarn types passes
  • yarn lint passes
  • yarn test — 3138 passed, 1 skipped
  • yarn test-types will re-run against the live API on the next scheduled job (needs live credentials, not run locally)

The scheduled test-types job caught server-side app config fields
that types.ts was missing, causing the live GetApp response to fail
type checking (moderation_keyframe_video_enabled and others).
@oliverlaz
oliverlaz merged commit 18bc3cf into master Sep 7, 2026
7 checks passed
@oliverlaz
oliverlaz deleted the fix/app-config-response-type-drift branch September 7, 2026 09:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants