8000 [CI] Sync Mock Server by Stream-SDK-Bot · Pull Request #3669 · GetStream/stream-chat-swift · GitHub
[go: up one dir, main page]
Skip to content

[CI] Sync Mock Server #3669

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Merged
merged 3 commits into from
May 29, 2025
Merged

[CI] Sync Mock Server #3669

merged 3 commits into from
May 29, 2025

Conversation

Stream-SDK-Bot
Copy link
Collaborator
@Stream-SDK-Bot Stream-SDK-Bot commented May 15, 2025 •
edited by coderabbitai bot
Loading

This PR was created automatically by CI.

Summary by CodeRabbit

  • Chores
    • Refreshed mock server JSON fixtures with updated IDs, timestamps, URLs, and minor field reordering to reflect more recent data snapshots.
    • Updated attachment, message, and event fixtures with new resource links and metadata.
    • No changes to application features or user-facing functionality.

@Stream-SDK-Bot Stream-SDK-Bot requested a review from a team as a code owner May 15, 2025 00:15
@github-actions GitHub Actions
Copy link
1 Warning
⚠️ Big PR

Generated by 🚫 Danger

@testableapple testableapple enabled auto-merge (squash) May 20, 2025 09:15
@coderabbitai coderabbitai
Copy link
coderabbitai bot commented May 29, 2025 •
edited
Loading

Walkthrough

A series of JSON fixture files used by the StreamChatTestMockServer were updated. Changes include refreshing all UUIDs, timestamps, and some user/device metadata to reflect later dates in May 2025. Minor reordering and relocation of user fields were performed, and some URLs and durations were updated. No schema or logic changes occurred.

Changes

Files/Groups Change Summary
http_add_member.json, http_channel_creation.json, http_channel_removal.json, http_channels.json, http_events.json, http_giphy_link.json, http_message.json, http_message_ephemeral.json, http_reaction.json, http_truncate.json, http_unsplash_link.json, http_youtube_link.json Updated IDs, timestamps, and some user/device fields; minor reordering of fields; updated durations and URLs where relevant. No schema changes.
http_attachment.json Updated the "file" URL and "duration" field.
ws_events.json, ws_events_channel.json, ws_events_member.json, ws_health_check.json, ws_message.json, ws_reaction.json Updated event/channel/message/user IDs, timestamps, device lists, and field orderings; no schema changes.

Poem

In a warren of JSON, fresh dates now bloom,
IDs and timestamps swept away the gloom.
URLs refreshed, durations anew,
Devices and fields found places true.
No code was harmed, just data revived—
The fixtures are ready, the tests have arrived!
🐇✨

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 5cd4e36 and e394383.

📒 Files selected for processing (19)
  • TestTools/StreamChatTestMockServer/Fixtures/JSONs/http_add_member.json (7 hunks)
  • TestTools/StreamChatTestMockServer/Fixtures/JSONs/http_attachment.json (1 hunks)
  • TestTools/StreamChatTestMockServer/Fixtures/JSONs/http_channel_creation.json (9 hunks)
  • TestTools/StreamChatTestMockServer/Fixtures/JSONs/http_channel_removal.json (8 hunks)
  • TestTools/StreamChatTestMockServer/Fixtures/JSONs/http_channels.json (11 hunks)
  • TestTools/StreamChatTestMockServer/Fixtures/JSONs/http_events.json (2 hunks)
  • TestTools/StreamChatTestMockServer/Fixtures/JSONs/http_giphy_link.json (5 hunks)
  • TestTools/StreamChatTestMockServer/Fixtures/JSONs/http_message.json (4 hunks)
  • TestTools/StreamChatTestMockServer/Fixtures/JSONs/http_message_ephemeral.json (5 hunks)
  • TestTools/StreamChatTestMockServer/Fixtures/JSONs/http_reaction.json (9 hunks)
  • TestTools/StreamChatTestMockServer/Fixtures/JSONs/http_truncate.json (13 hunks)
  • TestTools/StreamChatTestMockServer/Fixtures/JSONs/http_unsplash_link.json (5 hunks)
  • TestTools/StreamChatTestMockServer/Fixtures/JSONs/http_youtube_link.json (4 hunks)
  • TestTools/StreamChatTestMockServer/Fixtures/JSONs/ws_events.json (3 hunks)
  • TestTools/StreamChatTestMockServer/Fixtures/JSONs/ws_events_channel.json (14 hunks)
  • TestTools/StreamChatTestMockServer/Fixtures/JSONs/ws_events_member.json (5 hunks)
  • TestTools/StreamChatTestMockServer/Fixtures/JSONs/ws_health_check.json (3 hunks)
  • TestTools/StreamChatTestMockServer/Fixtures/JSONs/ws_message.json (5 hunks)
  • TestTools/StreamChatTestMockServer/Fixtures/JSONs/ws_reaction.json (4 hunks)
⏰ Context from checks skipped due to timeout of 90000ms (4)
  • GitHub Check: Test LLC (Debug)
  • GitHub Check: Build Test App and Frameworks
  • GitHub Check: Automated Code Review
  • GitHub Check: Metrics
🔇 Additional comments (71)
TestTools/StreamChatTestMockServer/Fixtures/JSONs/ws_health_check.json (1)

2-2: Approve fixture data refresh
These updates solely refresh the connection_id, user timestamps, and reorder metadata fields in the health-check mock. No schema or structural changes introduced.

Also applies to: 11-11, 14-14, 33-34, 38-38

TestTools/StreamChatTestMockServer/Fixtures/JSONs/http_add_member.json (1)

3-8: Approve fixture data refresh
Channel IDs, CIDs, timestamps, and member metadata have been advanced to May 2025 with minor field reorderings. No structural or semantic changes.

Also applies to: 17-20, 23-25, 136-137, 157-157, 162-163, 180-184, 186-188, 234-234

TestTools/StreamChatTestMockServer/Fixtures/JSONs/http_truncate.json (1)

2-2: Approve fixture data refresh
All mock values—durations, channel/message UUIDs, truncated timestamps, and member metadata—are updated to a mid-May 2025 snapshot. No schema alterations.

Also applies to: 4-4, 6-6, 8-9, 18-18, 21-21, 49-50, 70-70, 75-76, 93-93, 96-96, 197-197, 206-206, 209-209, 219-219, 248-250

TestTools/StreamChatTestMockServer/Fixtures/JSONs/ws_message.json (1)

3-6: Approve fixture data refresh
WebSocket event metadata, nested message IDs/timestamps, device entries, and user attributes have been refreshed for May 15, 2025. Schema remains unchanged.

Also applies to: 11-14, 26-108, 222-224, 247-253

TestTools/StreamChatTestMockServer/Fixtures/JSONs/http_attachment.json (1)

2-3: Approve fixture data refresh
The attachment URL and duration field have been updated to the latest snapshot. No structural or semantic changes.

TestTools/StreamChatTestMockServer/Fixtures/JSONs/http_message.json (1)

3-3: No semantic changes in HTTP message fixture – approving data refresh

All modifications are limited to advancing UUIDs, timestamps (updated_at, last_active, created_at/updated_at of the message), the channel ID (cid), and the duration field. The JSON schema and structure remain unchanged.

Also applies to: 15-15, 18-18, 32-34, 49-49

TestTools/StreamChatTestMockServer/Fixtures/JSONs/ws_events.json (1)

3-4: WS event fixture only updated with new IDs and timestamps – approving

This WebSocket “typing.start” fixture sees only UUIDs (cid, channel_id, device ids), timestamp advances (updated_at, last_active, device created_at, event created_at), and minor user‐field reordering (pando, birthland, type). No schema or structural changes.

Also applies to: 14-18, 32-61, 206-209, 211-211

TestTools/StreamChatTestMockServer/Fixtures/JSONs/http_channel_creation.json (1)

3-7: HTTP channel creation fixture refreshed – approving

All changes update channel/user/member UUIDs, various created_at/updated_at/last_active timestamps, and the final duration. No changes to keys or JSON structure.

Also applies to: 16-20, 22-24, 31-31, 137-137, 157-157, 179-179, 201-203, 227-229, 257-258, 285-286, 294-294

TestTools/StreamChatTestMockServer/Fixtures/JSONs/http_unsplash_link.json (1)

3-3: Unsplash link fixture data bumped – approving

Only the message id, user timestamps (updated_at, last_active), attachment URLs (image_url, thumb_url), cid, message timestamps, and overall duration were updated. Schema intact.

Also applies to: 15-15, 18-18, 32-33, 43-45, 60-60

TestTools/StreamChatTestMockServer/Fixtures/JSONs/http_events.json (1)

4-5: HTTP event fixture refreshed – approving

All edits are new cid/channel_id, advanced user timestamps (updated_at, last_active), repositioning of pando/birthland, updated event created_at, and duration. No structural changes.

Also applies to: 14-18, 22-23, 25-25, 27-27

TestTools/StreamChatTestMockServer/Fixtures/JSONs/http_youtube_link.json (5)

3-3: Refresh message ID only
The message id was updated to a new UUID as part of the data refresh. No schema change.

15-23: Update user timestamps and metadata
The user object’s updated_at, last_active, and additional fields (type, pando, birthland) were refreshed and reordered purely as data updates.

44-47: Refresh message-level metadata
The cid, created_at, and updated_at values on the message were bumped to May 2025 for consistency across fixtures.

50-52: Reorder and refresh i18n entries
The fr_text field was moved above zh_text and the language key was repositioned; values remain the same. Data-only change.

61-61: Update duration metric
Test fixture latency duration updated to 404.43ms. No impact on schema or logic.

TestTools/StreamChatTestMockServer/Fixtures/JSONs/http_channel_removal.json (7)

2-9: Refresh channel metadata and duration
The top‐level duration, channel id, cid, and its created_at/updated_at/deleted_at timestamps were advanced to May 2025. Purely a data refresh.

32-33: Update member timestamps for count_dooku
The membership created_at and updated_at values for count_dooku were refreshed. No schema change.

53-53: Update member data for han_solo
The user’s last_active and the membership’s created_at/updated_at for han_solo were bumped to mid-May 2025 as part of the data sync.

Also applies to: 58-59

76-79: Update member data for luke_skywalker
The user’s updated_at/last_active and corresponding membership timestamps were refreshed. Data-only update.

Also applies to: 87-88

108-110: Update member data for leia_organa
The user’s last_active, birthland, and the membership’s created_at/updated_at were updated to May 2025.

Also applies to: 121-122

132-132: Refresh channel config timestamp
The channel config updated_at was advanced. No schema or structural changes.

179-179: Refresh truncation metadata
The truncated_at timestamp and the truncated_by user’s updated_at/last_active were updated. Data-only change.

Also applies to: 188-188, 191-191

TestTools/StreamChatTestMockServer/Fixtures/JSONs/http_giphy_link.json (6)

3-3: Refresh message ID only
This GIF message id was updated to a new UUID. No logic change.

15-18: Update user timestamps
The user’s updated_at and last_active fields were bumped to mid-May 2025. Data-only.

31-33: Update media asset URLs
The image_url, thumb_url, and asset_url now point to media2.giphy.com with refreshed paths. Test data update only.

43-45: Refresh message-level metadata
The cid, created_at, and updated_at fields were updated to reflect May 2025.

49-51: Reorder and refresh i18n entries
The fr_text was moved above zh_text, and language was repositioned. Data-only.

60-60: Update duration metric
Latency duration updated to 363.19ms. No schema impact.

TestTools/StreamChatTestMockServer/Fixtures/JSONs/ws_events_member.json (5)

3-5: Refresh event identifiers
The event’s cid and channel_id were updated to new UUIDs for the mid-May 2025 snapshot.

14-15: Update member user activity
Inside member.user, the last_active and last_engaged_at were bumped to May 2025. Data-only.

32-33: Refresh membership timestamps
The member object’s created_at and updated_at were advanced to mid-May 2025.

49-50: Update top-level user data
The top‐level user’s last_active, last_engaged_at, image, and birthland were refreshed. Data sync only.

Also applies to: 54-55

66-67: Update event timing
The channel_last_message_at and event created_at were bumped to May 2025. Data-only.

TestTools/StreamChatTestMockServer/Fixtures/JSONs/http_channels.json (9)

5-9: Refresh channel header and timestamps
The channel id, cid, created_at, and updated_at were updated for the mid-May 2025 data sync, along with the top-level duration.

18-21: Update created_by user activity
The created_by user’s updated_at and last_active fields were refreshed to May 2025.

33-33: Refresh channel config timestamp
The config.updated_at was bumped to maintain consistency.

140-140: Update read-entry for count_dooku
The last_read timestamp was advanced to May 2025.

154-159: Update read-entry for han_solo
The user’s last_active and last_read were refreshed for the mid-May 2025 snapshot.

170-178: Update read-entry for luke_skywalker
Refreshed updated_at, last_active, pando, birthland, and last_read fields. Data-only.

Also applies to: 181-181

203-204: Refresh first membership timestamps
The first entry in members had its created_at and updated_at bumped to May 2025.

287-288: Refresh personal membership data
The membership object’s created_at and updated_at were advanced to mid-May 2025.

297-297: Update duration metric
Overall duration was updated to 197.59ms. No impact on test logic.

TestTools/StreamChatTestMockServer/Fixtures/JSONs/http_message_ephemeral.json (5)

3-3: Refresh user metadata fields.

Updated the message user’s id, updated_at, and last_active, and added/repositioned the birthland and team properties to align with other fixtures.

Also applies to: 16-17, 19-20, 23-24

30-31: Update Giphy attachment variants.

All title_link, thumb_url, and each variant’s url, width, height, size, and frames have been refreshed to the new GIF asset and metrics.

Also applies to: 56-62, 64-68, 71-75, 78-82, 85-88, 93-95, 99-102

114-116: Advance message timestamps and CID.

The message cid, created_at, and updated_at fields have been advanced to mid-May 2025.

132-133: Verify placement of args under command_info.

The args field remains outside the command_info object, whereas related fixtures may nest it. Please confirm this matches the mock-server schema.

135-135: Update duration metric.

Refreshed the duration from “51.43ms” to “284.58ms” to reflect the new timing.

TestTools/StreamChatTestMockServer/Fixtures/JSONs/ws_reaction.json (6)

3-5: Advance WebSocket event identifiers.

Refreshed the top-level cid and channel_id, plus message-level cid and event timestamps to mid-May 2025.

Also applies to: 76-78

7-7: Update message ID.

Advanced the inner message.id to the new UUID.

16-18: Refresh message author metadata.

Updated updated_at, last_active, and last_engaged_at for the message’s user, and repositioned the name field for consistency.

Also applies to: 23-23

33-33: Refresh latest_reactions entry.

Updated the reaction’s message_id, user timestamps within the reaction object, and the reaction’s own created_at/updated_at.

Also applies to: 40-42, 55-56

70-71: Advance reaction group timestamps.

Updated first_reaction_at and last_reaction_at under reaction_groups.like.

93-93: Update top-level reaction object.

Refreshed the reaction.message_id, author timestamps, and the reaction’s created_at and updated_at.

Also applies to: 100-102, 115-116

TestTools/StreamChatTestMockServer/Fixtures/JSONs/http_reaction.json (9)

3-3: Refresh HTTP message ID.

Updated the message.id to the new UUID.

15-18: Advance HTTP message user metadata.

Updated the user.updated_at, last_active, and re-ordered/added pando, birthland, and team.

Also applies to: 21-23

28-28: Update latest_reactions.message_id.

Refreshed the message_id in the first latest_reactions entry.

50-51: Advance latest_reactions timestamps.

Updated the created_at and updated_at for that entry.

56-56: Refresh own_reactions fields.

Updated the message_id and its created_at/updated_at.

Also applies to: 78-79

92-93: Advance reaction group times.

Updated first_reaction_at and last_reaction_at under reaction_groups.like.

98-100: Update HTTP message CID and metadata timestamps.

Advanced the cid, created_at, and updated_at for the HTTP message.

138-139: Refresh HTTP reaction timestamps.

Updated the reaction.created_at and updated_at fields.

142-142: Update HTTP request duration.

Refreshed the duration from “26.90ms” to “41.53ms”.

TestTools/StreamChatTestMockServer/Fixtures/JSONs/ws_events_channel.json (9)

3-5: Refresh top-level channel event metadata.

Updated created_at, cid, channel_last_message_at, and channel_id to mid-May 2025.

Also applies to: 8-8

10-15: Advance channel object timestamps.

Updated id, cid, last_message_at, created_at, and updated_at within the channel object.

24-28: Update channel creator timestamps.

Advanced the created_by.user.updated_at and last_active to the new snapshot.

42-214: Refresh channel creator’s devices.

All device ids and created_at timestamps under channel.created_by.devices have been updated to the new dates.

338-340: Advance Count Dooku membership timestamps.

Updated the created_at and updated_at for the count_dooku member entry.

359-384: Refresh Han Solo user and membership data.

Han Solo’s last_active, device entries, and membership created_at/updated_at fields have been updated.

Also applies to: 538-539

774-792: Advance Leia Organa’s activity and membership timestamps.

Updated Leia Organa’s last_active, device entries, and membership created_at/updated_at to mid-May 2025.

Also applies to: 967-969

979-979: Update channel configuration timestamp.

The config.updated_at field now reflects the new date.

1036-1044: Refresh final user metadata.

Updated the top-level user object’s updated_at, last_active, team, type, pando, and birthland.

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Explain this complex logic.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai explain this code block.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and explain its main purpose.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.
99D2

@testableapple testableapple merged commit 3a41957 into develop May 29, 2025
13 checks passed
@testableapple testableapple deleted the ci/sync-mock-server-1747268128 branch May 29, 2025 11:03
@coderabbitai coderabbitai bot mentioned this pull request Jun 1, 2025
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@testableapple testableapple testableapple approved these changes

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@Stream-SDK-Bot @testableapple
0