Files
3x-ui/web/service
MHSanaei 0296b2abd0 docs(port-conflict): refresh stale comments after the refactor
A few of the doc blocks in this file had drifted from what the code
actually does:

- inboundTransports' rule list claimed tunnel reads settings.network
  the same as shadowsocks. It doesn't — tunnel uses
  settings.allowedNetwork (3x-ui's wrapper around dokodemo-door).
- The "merge" hint above the settings-parsing block undersold what
  happens: SS / Tunnel override the streamSettings-derived bit while
  Mixed adds to it.
- portConflictDetail's example message and the checkPortConflict
  intro still mentioned "the old port-only check", a historical
  comparison that no longer says anything useful now that the
  transport-aware check is the only one.
- transportTagSuffix was documented as a generateInboundTag helper,
  but it's now also called by the conflict-error formatter.

Tighten the wording so future readers don't have to cross-check the
code against the doc.
2026-05-27 12:57:37 +02:00
..
v3
2026-05-10 02:13:42 +02:00
2026-05-19 12:20:24 +02:00
2026-05-19 12:20:24 +02:00
2026-05-19 12:20:24 +02:00
2026-05-19 12:20:24 +02:00
v3
2026-05-10 02:13:42 +02:00