mirror of
https://github.com/Dispatcharr/Dispatcharr.git
synced 2026-07-17 16:50:53 +00:00
a29704af55
The range-conflict warning classified each channel in the configured range as either this config's own auto-sync output or a real conflict, comparing each occupant against the source group. When a group sets a group_override, auto-sync creates its channels in the override target group, so the config's own channels failed that comparison and were misclassified as a conflict. - Add effectiveSyncGroupId to resolve the group the sync's channels actually land in (the group_override target when set, otherwise the source group). - Compare occupants against that effective target, so the config's own output is recognized while genuine conflicts (manual channels, channels from another account, channels in a different group, user-pinned numbers) still warn. - Add Vitest coverage for the helper, the override case, and an over-suppression guard, plus a backend test asserting the numbers-in-range endpoint reports the override target group. |
||
|---|---|---|
| .. | ||
| __init__.py | ||
| test_account_destroy.py | ||
| test_connection_pool.py | ||
| test_expiration_notifications.py | ||
| test_extinf_parsing.py | ||
| test_memory_cleanup.py | ||
| test_refresh_db_recovery.py | ||
| test_sync_compound.py | ||
| test_sync_correctness.py | ||
| test_xc_live_url.py | ||