@tencentcloud/sdk-mcp 1.3.8 → 1.3.9

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (70) hide show
  1. package/package.json +1 -1
  2. package/resource/doc/chatuikit/android/integration.md +466 -484
  3. package/resource/doc/chatuikit/android/workflow.md +713 -0
  4. package/resource/doc/livekit/live/flutter/live-integration.md +208 -167
  5. package/resource/doc/livekit/voice/android/voice-audience-list.md +335 -0
  6. package/resource/doc/livekit/voice/android/voice-audio-effect.md +384 -0
  7. package/resource/doc/livekit/voice/android/voice-barrage.md +569 -0
  8. package/resource/doc/livekit/voice/android/voice-co-guest-interaction.md +748 -0
  9. package/resource/doc/livekit/voice/android/voice-gift.md +833 -0
  10. package/resource/doc/livekit/voice/android/voice-host-interaction.md +728 -0
  11. package/resource/doc/livekit/voice/android/voice-integration.md +886 -0
  12. package/resource/doc/livekit/voice/android/voice-room-list.md +493 -0
  13. package/resource/doc/livekit/voice/android/workflow.md +333 -0
  14. package/resource/doc/livekit/voice/flutter/voice-audience-list.md +337 -0
  15. package/resource/doc/livekit/voice/flutter/voice-audio-effect.md +739 -0
  16. package/resource/doc/livekit/voice/flutter/voice-barrage.md +578 -0
  17. package/resource/doc/livekit/voice/flutter/voice-co-guest-interaction.md +673 -0
  18. package/resource/doc/livekit/voice/flutter/voice-gift.md +812 -0
  19. package/resource/doc/livekit/voice/flutter/voice-integration.md +925 -0
  20. package/resource/doc/livekit/voice/flutter/voice-room-list.md +842 -0
  21. package/resource/doc/livekit/voice/flutter/workflow.md +359 -0
  22. package/resource/doc/livekit/voice/ios/voice-audience-list.md +335 -0
  23. package/resource/doc/livekit/voice/ios/voice-audio-effect.md +373 -0
  24. package/resource/doc/livekit/voice/ios/voice-barrage.md +529 -0
  25. package/resource/doc/livekit/voice/ios/voice-co-guest-interaction.md +701 -0
  26. package/resource/doc/livekit/voice/ios/voice-gift.md +785 -0
  27. package/resource/doc/livekit/voice/ios/voice-host-interaction.md +820 -0
  28. package/resource/doc/livekit/voice/ios/voice-integration.md +853 -0
  29. package/resource/doc/livekit/voice/ios/voice-room-list.md +467 -0
  30. package/resource/doc/livekit/voice/ios/workflow.md +358 -0
  31. package/resource/doc/livekit/voice/uni-app/voice-audience-list.md +264 -0
  32. package/resource/doc/livekit/voice/uni-app/voice-audio-effect.md +332 -0
  33. package/resource/doc/livekit/voice/uni-app/voice-barrage.md +482 -0
  34. package/resource/doc/livekit/voice/uni-app/voice-co-guest-interaction.md +944 -0
  35. package/resource/doc/livekit/voice/uni-app/voice-gift.md +716 -0
  36. package/resource/doc/livekit/voice/uni-app/voice-integration.md +613 -0
  37. package/resource/doc/livekit/voice/uni-app/voice-room-list.md +562 -0
  38. package/resource/doc/livekit/voice/uni-app/workflow.md +369 -0
  39. package/resource/doc/roomkit/vue/integration.md +119 -224
  40. package/resource/doc/roomkit/vue/workflow.md +472 -226
  41. package/resource/doc/tuicallkit/android/integration.md +675 -90
  42. package/resource/doc/tuicallkit/android/workflow.md +432 -0
  43. package/tools/common/present-scenario-choice.js +16 -0
  44. package/tools/common/present-scenario-choice.js.map +1 -0
  45. package/tools/definitions/get_native_call_uikit_integration_def.js +18 -2
  46. package/tools/definitions/get_native_call_uikit_integration_def.js.map +1 -1
  47. package/tools/definitions/get_native_chat_uikit_integration_def.js +29 -7
  48. package/tools/definitions/get_native_chat_uikit_integration_def.js.map +1 -1
  49. package/tools/definitions/get_native_live_uikit_integration_def.js +65 -40
  50. package/tools/definitions/get_native_live_uikit_integration_def.js.map +1 -1
  51. package/tools/definitions/get_native_live_uikit_interaction_def.js +42 -94
  52. package/tools/definitions/get_native_live_uikit_interaction_def.js.map +1 -1
  53. package/tools/definitions/get_web_room_feature_detail_def.js +29 -32
  54. package/tools/definitions/get_web_room_feature_detail_def.js.map +1 -1
  55. package/tools/definitions/get_web_room_uikit_integration_def.js +25 -9
  56. package/tools/definitions/get_web_room_uikit_integration_def.js.map +1 -1
  57. package/tools/definitions/present_scenario_choice_def.js +53 -0
  58. package/tools/definitions/present_scenario_choice_def.js.map +1 -0
  59. package/tools/definitions/record_prompt_def.js +6 -1
  60. package/tools/definitions/record_prompt_def.js.map +1 -1
  61. package/tools/definitions/record_result_def.js +20 -4
  62. package/tools/definitions/record_result_def.js.map +1 -1
  63. package/tools/index.js +2 -0
  64. package/tools/index.js.map +1 -1
  65. package/tools/live/get-native-live-uikit-integration.js +110 -34
  66. package/tools/live/get-native-live-uikit-integration.js.map +1 -1
  67. package/tools/live/get_native_live_uikit_interaction.js +128 -35
  68. package/tools/live/get_native_live_uikit_interaction.js.map +1 -1
  69. package/utils/report-cls-client.js +1 -1
  70. package/utils/report-es-client.js +1 -1
@@ -0,0 +1,467 @@
1
+ `LiveListStore` 是 `AtomicXCore` 中负责管理直播房间列表、创建、加入以及维护房间状态的核心模块。通过`LiveListStore`,您可以为您的应用构建完整的直播生命周期管理。
2
+
3
+ ![](https://write-document-release-1258344699.cos.ap-guangzhou.tencentcos.cn/100027182498/6fd3c4f2ab6011f0b5345254005ef0f7.png)
4
+
5
+
6
+ ## 核心功能
7
+ - **直播列表拉取**:获取当前所有公开的直播间列表,支持分页加载。
8
+
9
+ - **直播生命周期管理**:提供从创建、开播、加入、离开到结束直播的全套流程接口。
10
+
11
+ - **直播信息更新**:主播可以随时更新直播间的公开信息,例如封面、公告等。
12
+
13
+ - **实时事件监听**:监听直播结束、用户被踢出等关键事件。
14
+
15
+ - **自定义业务数据**:强大的自定义元数据(`MetaData`)能力,允许您在房间内存储和同步任何业务相关的信息,例如直播状态、音乐信息、自定义角色等 。
16
+
17
+
18
+ ## 核心概念
19
+
20
+ 在开始集成之前,我们先通过下表了解一下 `LiveListStore` 相关的几个核心概念:
21
+ <table>
22
+ <tr>
23
+ <td rowspan="1" colSpan="1" >**核心概念**</td>
24
+
25
+ <td rowspan="1" colSpan="1" >**类型**</td>
26
+
27
+ <td rowspan="1" colSpan="1" >**核心职责与描述**</td>
28
+ </tr>
29
+
30
+ <tr>
31
+ <td rowspan="1" colSpan="1" >`LiveInfo`</td>
32
+
33
+ <td rowspan="1" colSpan="1" >`struct`</td>
34
+
35
+ <td rowspan="1" colSpan="1" >代表一个直播间的所有信息模型。包含了直播ID (`liveID`)、名称 (`liveName`)、房主信息 (`liveOwner`) 以及自定义元数据 (`metaData`) 等。</td>
36
+ </tr>
37
+
38
+ <tr>
39
+ <td rowspan="1" colSpan="1" >`LiveListState`</td>
40
+
41
+ <td rowspan="1" colSpan="1" >`struct`</td>
42
+
43
+ <td rowspan="1" colSpan="1" >代表直播列表模块的当前状态。其核心属性 liveList 是一个 `[LiveInfo] `数组,存储了拉取到的直播列表;`currentLive` 则代表用户当前所在的直播间信息。</td>
44
+ </tr>
45
+
46
+ <tr>
47
+ <td rowspan="1" colSpan="1" >`LiveListEvent`</td>
48
+
49
+ <td rowspan="1" colSpan="1" >`enum`</td>
50
+
51
+ <td rowspan="1" colSpan="1" >代表直播房间的全局事件。分为 `.onLiveEnded` (直播结束) 和 `.onKickedOutOfLive` (被踢出直播) 两种,用于处理关键的房间状态变更。</td>
52
+ </tr>
53
+
54
+ <tr>
55
+ <td rowspan="1" colSpan="1" >`LiveListStore`</td>
56
+
57
+ <td rowspan="1" colSpan="1" >`class`</td>
58
+
59
+ <td rowspan="1" colSpan="1" >这是与直播列表和房间生命周期交互的核心管理类。它是一个全局单例 (shared),负责所有直播房间的创建、加入、信息更新等操作。</td>
60
+ </tr>
61
+ </table>
62
+
63
+
64
+ ## 实现步骤
65
+
66
+ ### 步骤1:组件集成
67
+
68
+ 请参考 [快速接入](https://write.woa.com/document/192834898445422592) 集成 **AtomicXCore**,并完成 [搭建基础语聊房](https://write.woa.com/document/192834898445422592)的功能实现。
69
+
70
+ ### 步骤2:实现观众从直播列表进入直播间
71
+
72
+ #### 实现方式:
73
+ 1. 创建一个展示直播列表的页面,该页面使用 `UICollectionView` 来布局直播间卡片。
74
+
75
+ 2. 当用户点击某个卡片时,获取该直播间的 `liveID`,并跳转到观众观看页面。
76
+
77
+ ``` swift
78
+ class LiveListViewController: UIViewController, UICollectionViewDataSource, UICollectionViewDelegate, UICollectionViewDelegateFlowLayout {
79
+
80
+ private let liveListStore = LiveListStore.shared
81
+ private var cancellables = Set<AnyCancellable>()
82
+ private var liveList: [LiveInfo] = []
83
+
84
+ private var collectionView: UICollectionView!
85
+
86
+ override func viewDidLoad() {
87
+ super.viewDidLoad()
88
+ setupUI()
89
+ bindStore()
90
+ fetchLiveList()
91
+ }
92
+
93
+ private func bindStore() {
94
+ // 订阅 state,自动接收列表更新
95
+ liveListStore.state
96
+ .subscribe(StatePublisherSelector(keyPath: \LiveListState.liveList))
97
+ .removeDuplicates()
98
+ .receive(on: DispatchQueue.main)
99
+ .sink { [weak self] fetchedList in
100
+ self?.liveList = fetchedList
101
+ self?.collectionView.reloadData()
102
+ }
103
+ .store(in: &cancellables)
104
+ }
105
+
106
+ private func fetchLiveList() {
107
+ liveListStore.fetchLiveList(cursor: "", count: 20) { result in
108
+ if case .failure(let error) = result {
109
+ print("直播列表拉取失败: \(error.localizedDescription)")
110
+ }
111
+ }
112
+ }
113
+
114
+ // 当用户点击列表中的某个Cell时
115
+ func collectionView(_ collectionView: UICollectionView, didSelectItemAt indexPath: IndexPath) {
116
+ let selectedLiveInfo = liveList[indexPath.item]
117
+
118
+ // 创建观众观看页面,并将 liveID 传入
119
+ let audienceVC = YourAudienceViewController(liveID: selectedLiveInfo.liveID)
120
+ audienceVC.modalPresentationStyle = .fullScreen
121
+ present(audienceVC, animated: true)
122
+ }
123
+
124
+ // --- UICollectionViewDataSource, Delegate, and UI setup methods ---
125
+ private func setupUI() {
126
+ let layout = UICollectionViewFlowLayout()
127
+ // ... (可以自定义您的布局)
128
+ collectionView = UICollectionView(frame: view.bounds, collectionViewLayout: layout)
129
+ collectionView.dataSource = self
130
+ collectionView.delegate = self
131
+ collectionView.register(UICollectionViewCell.self, forCellWithReuseIdentifier: "LiveCell")
132
+ view.addSubview(collectionView)
133
+ }
134
+
135
+ func collectionView(_ collectionView: UICollectionView, numberOfItemsInSection section: Int) -> Int {
136
+ return liveList.count
137
+ }
138
+
139
+ func collectionView(_ collectionView: UICollectionView, cellForItemAt indexPath: IndexPath) -> UICollectionViewCell {
140
+ let cell = collectionView.dequeueReusableCell(withReuseIdentifier: "LiveCell", for: indexPath)
141
+ cell.backgroundColor = .lightGray // 自定义您的Cell样式
142
+ // let liveInfo = liveList[indexPath.item]
143
+ // ... (例如: cell.titleLabel.text = liveInfo.liveName)
144
+ return cell
145
+ }
146
+
147
+ func collectionView(_ collectionView: UICollectionView, layout collectionViewLayout: UICollectionViewLayout, sizeForItemAt indexPath: IndexPath) -> CGSize {
148
+ // 单列、双列布局可通过自定义您的Cell大小来实现
149
+ let width = (view.bounds.width - 30) / 2
150
+ return CGSize(width: width, height: width * 1.2)
151
+ }
152
+ }
153
+ ```
154
+
155
+ **LiveInfo 参数说明**
156
+
157
+ <table>
158
+ <tr>
159
+ <td rowspan="1" colSpan="1" >**参数名**</td>
160
+
161
+ <td rowspan="1" colSpan="1" >**类型**</td>
162
+
163
+ <td rowspan="1" colSpan="1" >**描述**</td>
164
+ </tr>
165
+
166
+ <tr>
167
+ <td rowspan="1" colSpan="1" >`liveID`</td>
168
+
169
+ <td rowspan="1" colSpan="1" >`String`</td>
170
+
171
+ <td rowspan="1" colSpan="1" >直播间的唯一标识符</td>
172
+ </tr>
173
+
174
+ <tr>
175
+ <td rowspan="1" colSpan="1" >`liveName`</td>
176
+
177
+ <td rowspan="1" colSpan="1" >`String`</td>
178
+
179
+ <td rowspan="1" colSpan="1" >直播间的标题</td>
180
+ </tr>
181
+
182
+ <tr>
183
+ <td rowspan="1" colSpan="1" >`coverURL`</td>
184
+
185
+ <td rowspan="1" colSpan="1" >`String`</td>
186
+
187
+ <td rowspan="1" colSpan="1" >直播间的封面图片地址</td>
188
+ </tr>
189
+
190
+ <tr>
191
+ <td rowspan="1" colSpan="1" >`liveOwner`</td>
192
+
193
+ <td rowspan="1" colSpan="1" >[LiveUserInfo](https://tencent-rtc.github.io/TUIKit_iOS/documentation/atomicxcore/liveuserinfo)</td>
194
+
195
+ <td rowspan="1" colSpan="1" >房主的个人信息</td>
196
+ </tr>
197
+
198
+ <tr>
199
+ <td rowspan="1" colSpan="1" >`totalViewerCount`</td>
200
+
201
+ <td rowspan="1" colSpan="1" >`Int`</td>
202
+
203
+ <td rowspan="1" colSpan="1" >直播间的总观看人数</td>
204
+ </tr>
205
+
206
+ <tr>
207
+ <td rowspan="1" colSpan="1" >`categoryList`</td>
208
+
209
+ <td rowspan="1" colSpan="1" >`[NSNumber]`</td>
210
+
211
+ <td rowspan="1" colSpan="1" >直播间的分类标签列表</td>
212
+ </tr>
213
+
214
+ <tr>
215
+ <td rowspan="1" colSpan="1" >`notice`</td>
216
+
217
+ <td rowspan="1" colSpan="1" >`String`</td>
218
+
219
+ <td rowspan="1" colSpan="1" >直播间的公告信息</td>
220
+ </tr>
221
+
222
+ <tr>
223
+ <td rowspan="1" colSpan="1" >`metaData`</td>
224
+
225
+ <td rowspan="1" colSpan="1" >`[String: String]`</td>
226
+
227
+ <td rowspan="1" colSpan="1" >开发者自定义的元数据,用于实现复杂的业务场景</td>
228
+ </tr>
229
+ </table>
230
+
231
+
232
+ ## 功能进阶
233
+
234
+ ### 场景一:实现直播列表的分类展示
235
+
236
+ 在 App 的直播广场页,顶部设有“热门”、“音乐”、“游戏”等分类标签。用户点击不同的标签后,下方的直播列表会动态筛选,只展示对应分类的直播间,从而帮助用户快速发现感兴趣的内容。
237
+
238
+ ![](https://write-document-release-1258344699.cos.ap-guangzhou.tencentcos.cn/100027182498/7dcde616ab4b11f0a68e5254001c06ec.png)
239
+
240
+
241
+ #### 实现方式:
242
+
243
+ 核心是利用 `LiveInfo` 模型中的 `categoryList` 属性。
244
+ 1. 当主播开播设置分类后,`fetchLiveList` 返回的 `LiveInfo` 对象中就会包含这些分类信息。
245
+
246
+ 2. 您的 App 在获取到完整的直播列表后,只需在客户端根据用户选择的分类,对这个列表进行一次简单的筛选,然后刷新 UI 即可。
247
+
248
+
249
+ #### 代码示例:
250
+
251
+ 以下示例展示了如何在 `LiveListViewController` 中扩展一个 `LiveListManager` 来处理数据和筛选逻辑。
252
+ ``` swift
253
+ import AtomicXCore
254
+ import Combine
255
+
256
+ // 1. 创建一个数据管理器来封装数据获取和筛选逻辑
257
+ class LiveListManager {
258
+ private let liveListStore = LiveListStore.shared
259
+ private var cancellables = Set<AnyCancellable>()
260
+ private var fullLiveList: [LiveInfo] = []
261
+
262
+ // 对外暴露最终的直播列表
263
+ let filteredLiveListPublisher = CurrentValueSubject<[LiveInfo], Never>([])
264
+
265
+ init() {
266
+ liveListStore.state
267
+ .subscribe(StatePublisherSelector(keyPath: \LiveListState.liveList))
268
+ .receive(on: DispatchQueue.main)
269
+ .sink { [weak self] fetchedList in
270
+ self?.fullLiveList = fetchedList
271
+ // 默认将完整列表发布出去
272
+ self?.filteredLiveListPublisher.send(fetchedList)
273
+ }
274
+ .store(in: &cancellables)
275
+ }
276
+
277
+ func fetchFirstPage() {
278
+ liveListStore.fetchLiveList(cursor: "", count: 20) { _ in }
279
+ }
280
+
281
+ /// 根据分类筛选直播列表
282
+ func filterLiveList(by categoryId: NSNumber?) {
283
+ guard let categoryId = categoryId else {
284
+ // 如果 categoryId 为 nil,则显示完整列表
285
+ filteredLiveListPublisher.send(fullLiveList)
286
+ return
287
+ }
288
+
289
+ let filteredList = fullLiveList.filter { liveInfo in
290
+ liveInfo.categoryList.contains(categoryId)
291
+ }
292
+ filteredLiveListPublisher.send(filteredList)
293
+ }
294
+ }
295
+ ```
296
+ ``` swift
297
+ // 2. 在您的 LiveListViewController 中使用 Manager
298
+ class LiveListViewController: UIViewController {
299
+ private let manager = LiveListManager()
300
+ private var cancellables = Set<AnyCancellable>()
301
+ private var liveList: [LiveInfo] = []
302
+ private var collectionView: UICollectionView!
303
+
304
+ override func viewDidLoad() {
305
+ super.viewDidLoad()
306
+ // ... setupUI ...
307
+
308
+
309
+ // 绑定数据
310
+ manager.filteredLiveListPublisher
311
+ .receive(on: DispatchQueue.main)
312
+ .sink { [weak self] filteredList in
313
+ self?.liveList = filteredList
314
+ self?.collectionView.reloadData()
315
+ }
316
+ .store(in: &cancellables)
317
+
318
+
319
+ // 首次拉取
320
+ manager.fetchFirstPage()
321
+ }
322
+
323
+
324
+ // 当用户点击顶部分类标签 (UISegmentedControl) 时
325
+ @objc func categorySegmentDidChange(_ sender: UISegmentedControl) {
326
+ let selectedCategoryId: NSNumber? = 1 // 假设 "音乐" 分类的ID是 1
327
+ manager.filterLiveList(by: selectedCategoryId)
328
+ }
329
+
330
+
331
+ // ... (UICollectionView 相关代码)
332
+ }
333
+
334
+ ```
335
+
336
+ ### 场景二:实现语聊房内的自定义状态同步
337
+
338
+ 在语聊房中,主播可能需要向所有观众同步一些自定义信息,例如“当前房间话题”、“背景音乐信息”等。`LiveListStore` 的 `MetaData` 功能可以实现这一点。
339
+
340
+ #### 实现方式:
341
+ 1. 主播端将自定义信息(建议使用 JSON 格式)通过 `updateLiveMetaData` 接口设置到一个或多个 key 中。`AtomicXCore` 会将这个变更实时同步给所有观众。
342
+
343
+ 2. 观众端只需订阅` LiveListState.currentLive`,监听 `metaData` 的变化,一旦发现关心的 key 更新,就解析其 value 并刷新业务状态。
344
+
345
+
346
+ #### 示例代码:
347
+ ``` swift
348
+ import AtomicXCore
349
+ import Combine
350
+
351
+ // 1. 定义一个背景音乐模型 (可选,建议使用 Codable)
352
+ struct MusicModel: Codable {
353
+ let musicId: String
354
+ let musicName: String
355
+ }
356
+
357
+ // 2. 主播端:在您的主播业务逻辑中,添加推送背景音乐的方法
358
+ func updateBackgroundMusic(music: MusicModel) {
359
+ guard let jsonData = try? JSONEncoder().encode(music),
360
+ let jsonString = String(data: jsonData, encoding: .utf8) else { return }
361
+
362
+ // 将要更新的元数据
363
+ let metaData = ["music_info": jsonString]
364
+
365
+ // 使用全局单例的 liveListStore 来更新 metaData
366
+ LiveListStore.shared.updateLiveMetaData(metaData) { result in
367
+ if case .success = result {
368
+ print("背景音乐 \(music.musicName) 推送成功")
369
+ } else if case .failure(let error) = result {
370
+ print("背景音乐推送失败: \(error.message)")
371
+ }
372
+ }
373
+ }
374
+
375
+ // 3. 观众端:在您的观众业务逻辑中,订阅并响应
376
+ private func subscribeToDataUpdates() {
377
+ LiveListStore.shared.state
378
+ // 监听当前房间的 metaData
379
+ .subscribe(StatePublisherSelector(keyPath: \LiveListState.currentLive))
380
+ .map { $0.metaData["music_info"]}
381
+ .removeDuplicates()
382
+ .receive(on: DispatchQueue.main)
383
+ .sink { jsonString in
384
+ guard let jsonString = jsonString,
385
+ let data = jsonString.data(using: .utf8),
386
+ let music = try? JSONDecoder().decode(MusicModel.self, from: data) else {
387
+ // 刷新业务状态,播放新的音乐
388
+ // ... (例如: playMusic(music))
389
+ return
390
+ }
391
+
392
+ }
393
+ .store(in: &cancellables)
394
+ }
395
+
396
+ ```
397
+
398
+ 关于 [LiveListStore](https://tencent-rtc.github.io/TUIKit_iOS/documentation/atomicxcore/liveliststore) 及其相关类的所有公开接口、属性和方法的详细信息,请参阅随 [AtomicXCore](https://tencent-rtc.github.io/TUIKit_iOS/documentation/atomicxcore) 框架的官方 API 文档。本文档使用到的相关 Store 如下:
399
+ <table>
400
+ <tr>
401
+ <td rowspan="1" colSpan="1" >**Store/Component**</td>
402
+
403
+ <td rowspan="1" colSpan="1" >**功能描述**</td>
404
+
405
+ <td rowspan="1" colSpan="1" >**API 文档**</td>
406
+ </tr>
407
+
408
+ <tr>
409
+ <td rowspan="1" colSpan="1" >LiveListStore</td>
410
+
411
+ <td rowspan="1" colSpan="1" >直播间全生命周期管理:创建 / 加入 / 离开 / 销毁房间,查询房间列表,修改直播信息(名称、公告等),监听直播状态(例如被踢出、结束)。</td>
412
+
413
+ <td rowspan="1" colSpan="1" >[API 文档](https://tencent-rtc.github.io/TUIKit_iOS/documentation/atomicxcore/liveliststore)</td>
414
+ </tr>
415
+ </table>
416
+
417
+
418
+ ## 常见问题
419
+
420
+ ### 语聊房的列表和视频直播的列表数据是同一份吗?
421
+
422
+ 它们的数据是同一份,您不需要分开拉取。`LiveListStore` 是一个全局单例,它负责统一管理应用中所有“直播”房间的生命周期,无论是视频直播还是语聊房。
423
+
424
+ ### **直播列表中如何区分语聊房和视频直播**
425
+
426
+ `LiveListStore` 本身不区分房间的业务类型。您需要在获取列表后,在客户端的应用层(业务逻辑或 UI 层)进行筛选和分类。
427
+
428
+ 我们推荐采用以下两种方式进行区分:
429
+
430
+ **方式一(推荐):使用 seatLayoutTemplateID 区分**。这是一个用于定义房间布局的模板 ID,关于目前已支持的模板 ID 和效果,请参阅文档[开始直播-运行效果](https://write.woa.com/document/191126382767431680)。您要在创建房间时指定 ID,然后在获取列表时根据 ID 范围来识别业务场景。
431
+ - **步骤1:创建房间时指定 ID **调用 LiveListStore.shared.createLive 时,您需要根据业务场景为 LiveInfo 的 seatLayoutTemplateID 属性传入指定范围的 ID:
432
+
433
+ - 语聊房场景:传入 1 - 199 范围内的模板 ID。
434
+
435
+ - 视频直播场景:传入 200 - 999 范围内的模板 ID。
436
+
437
+ - **步骤2:获取列表时筛选 **客户端在 `LiveListStore.state.liveList`中收到列表数据后,通过判断这个 ID 值所属的范围来区分,从而在进入直播间的时候区分两种业务场景。
438
+
439
+
440
+ > **重要提示:**
441
+ >
442
+
443
+ > 创建房间时,如果传入的 seatLayoutTemplateID 范围与您的业务场景(语聊房、视频直播)不匹配,可能会导致麦位布局出现功能异常。
444
+ >
445
+
446
+
447
+ **方式二**:**为 **`liveID`** 添加业务前缀。**这是一种可选的、纯粹的应用层约定,用于辅助您在客户端快速筛选。
448
+
449
+ - **步骤1:创建房间时添加前缀 **在您生成 liveID 并调用 createLive 时,为不同业务类型的 liveID 赋予不同的前缀。例如:视频直播的 ID 以 “Live_” 开头 (例如:Live_12345),语聊房的 ID 以 “voice_” 开头 (例如:voice_67890)。
450
+
451
+ - **步骤2:获取列表时检查前缀 **客户端在拉取到列表后,通过检查 liveID 字符串的前缀来进行区分。
452
+
453
+
454
+ ### 使用 `updateLiveMetaData` 时有哪些需要注意的限制和规则?
455
+
456
+ 为了保证系统的稳定和高效,`metaData` 的使用遵循以下规则:
457
+ - **权限**:只有房主和管理员可以调用 `updateLiveMetaData`。普通观众没有权限。
458
+
459
+ - **数量与大小限制:**
460
+
461
+ - 单个房间最多支持 **10** 个 key。
462
+
463
+ - 每个 key 的长度不超过 **50 字节**,每个 value 的长度不超过 **2KB**。
464
+
465
+ - 单个房间所有 value 的总大小不超过 **16KB**。
466
+
467
+ - **冲突解决**: `metaData` 的更新机制是“后来者覆盖”。如果多个管理员在短时间内修改同一个 key,最后一次的修改会生效。建议在业务设计上避免多人同时修改同一个关键信息。