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. |
||
|---|---|---|
| .. | ||
| migrations | ||
| tests | ||
| __init__.py | ||
| admin.py | ||
| api_urls.py | ||
| api_views.py | ||
| apps.py | ||
| connection_pool.py | ||
| forms.py | ||
| models.py | ||
| serializers.py | ||
| signals.py | ||
| tasks.py | ||
| urls.py | ||
| utils.py | ||
| views.py | ||