Skip to content

Commit d3ef075

Browse files
SERDUNclaude
andcommitted
fix(call): compare monitorCheckInterval directly to avoid spurious CallBloc updates
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
1 parent bad79b2 commit d3ef075

1 file changed

Lines changed: 4 additions & 2 deletions

File tree

lib/features/call/view/call_config_synchronizer.dart

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -44,8 +44,10 @@ class _CallConfigSynchronizerState extends State<CallConfigSynchronizer> {
4444
}
4545

4646
void _syncConfigs(FeatureAccess prev, FeatureAccess current) {
47-
if (prev.loggingConfig != current.loggingConfig) {
48-
_logger.info('LoggingConfig updated: ${prev.loggingConfig} -> ${current.loggingConfig}');
47+
if (prev.loggingConfig.monitorCheckInterval != current.loggingConfig.monitorCheckInterval) {
48+
_logger.info(
49+
'monitorCheckInterval updated: ${prev.loggingConfig.monitorCheckInterval} -> ${current.loggingConfig.monitorCheckInterval}',
50+
);
4951

5052
context.read<CallBloc>().add(
5153
CallConfigEvent.updated(monitorCheckInterval: current.loggingConfig.monitorCheckInterval),

0 commit comments

Comments
 (0)