{% extends 'generic/object.html' %}
{% load helpers %}

{% block content %}
<div class="row">
  <div class="col col-md-6">
    <div class="card">
      <h2 class="card-header">Auto-cabling</h2>
      <table class="table table-hover attr-table">
        {% comment %} object-level perms: the two PORT rows come from the view already scoped to the
           requesting user (see views._scoped) — never straight off `object`, which the plugin
           permission alone would hand out for every job of the install. The two RACK rows do
           come straight off `object`: a rack name is an inventory label, and the Path row below
           lists rack names for everyone. {% endcomment %}
        <tr>
          <th scope="row">Source port</th>
          <td>{{ source_port|linkify|placeholder }}
            {% if trace_source %}<a href="{{ trace_source }}" class="btn btn-sm btn-outline-secondary ms-2">Trace</a>{% endif %}
          </td>
        </tr>
        <tr>
          <th scope="row">Destination port</th>
          <td>{{ target_port|linkify|placeholder }}
            {% if trace_target %}<a href="{{ trace_target }}" class="btn btn-sm btn-outline-secondary ms-2">Trace</a>{% endif %}
          </td>
        </tr>
        <tr>
          <th scope="row">Source rack</th>
          <td>{{ object.source_rack|linkify|placeholder }}</td>
        </tr>
        <tr>
          <th scope="row">Target rack</th>
          <td>{{ object.target_rack|linkify|placeholder }}</td>
        </tr>
        <tr>
          <th scope="row">Media</th>
          <td>{{ object.media }}</td>
        </tr>
        <tr>
          <th scope="row">Status</th>
          <td>{% badge object.get_status_display bg_color=object.get_status_color %}</td>
        </tr>
        <tr>
          <th scope="row">Path</th>
          <td>
            {% if object.path %}{{ object.path|join:" → " }}{% else %}—{% endif %}
          </td>
        </tr>
        <tr>
          <th scope="row">Detail</th>
          <td>{{ object.reason|placeholder }}</td>
        </tr>
        <tr>
          <th scope="row">Requested by</th>
          <td>{{ object.requested_by|placeholder }}</td>
        </tr>
      </table>
    </div>
  </div>
  <div class="col col-md-6">
    <div class="card">
      <h2 class="card-header">
        Cables created by this job
        {% comment %} object-level perms: `cable_count` counts only what THIS viewer may see (plus the ids
           that match no cable at all, which the warning row below accounts for). The raw
           `object.created_cable_ids|length` told a restricted viewer how many cables the job
           holds beyond the rows it is shown. Same rule as the REST payload.
           It stays a count of the TRACE — the header says "created by this job", which a rolled-back
           job did create — so it is not restated per case: the invariant cable_count == rows shown +
           missing is what lets the row at the bottom of the table explain the whole gap, and a badge
           narrowed to the surviving rows would leave that row explaining a difference no longer
           visible anywhere on the page. {% endcomment %}
        <span class="badge text-bg-grey">{{ cable_count }}</span>
        {% if object.created_cable_ids %}
          <a href="{% url 'plugins:netbox_autocabling:workorder' %}?pk={{ object.pk }}"
             class="btn btn-sm btn-primary">⬇ Work order (Excel)</a>
        {% endif %}
        {% if object.created_cable_ids and object.status != 'rolled_back' %}
          {% comment %} the confirmation says what the button DESTROYS, so it is built from
             `deletable_count` (restrict(user, "delete") — the very queryset rollback deletes),
             never from the view-scoped badge above: delete and view are independent object
             permissions, and an operator granted delete without view was confirming
             "Delete the 0 cable(s)…" and destroying every one of them. {% endcomment %}
          <form method="post" class="float-end"
                action="{% url 'plugins:netbox_autocabling:cablingjob_rollback' object.pk %}"
                onsubmit="return confirm('Delete the {{ deletable_count }} cable(s) created by this job?');">
            {% csrf_token %}
            <button type="submit" class="btn btn-sm btn-danger">⟲ Roll back this job</button>
          </form>
          {% if deletable_count != cable_count %}
            {% comment %} the two numbers answer different questions; when they disagree the destructive
               one is spelled out on the page, so the modal is never a surprise. A count, not
               an identity: no row of a cable this viewer may not view is added anywhere. {% endcomment %}
            <span class="text-muted small ms-2">Rollback will delete {{ deletable_count }} cable(s).</span>
          {% endif %}
        {% endif %}
      </h2>
      <table class="table table-hover">
        <thead>
          <tr><th>Cable</th><th>Type</th><th>Status</th></tr>
        </thead>
        <tbody>
          {% for cable in cables %}
            <tr>
              <td>{{ cable|linkify }}</td>
              <td>{{ cable.type }}</td>
              <td>{{ cable.status }}</td>
            </tr>
          {% empty %}
            <tr><td colspan="3" class="text-muted">No cable (job not executed or rolled back).</td></tr>
          {% endfor %}
          {% if missing_cables > 0 %}
            {% comment %} only ids matching NO cable row reach here: "no longer exist" is a statement about
               the database, so a cable the viewer merely may not see must never land in it. WHY they are
               gone is `missing_state` (views + visibility.missing_cable_state): a rollback run through the
               plugin deletes the cables and KEEPS the trace, so it empties this table by design — and the
               single warning below used to accuse the operator's install of losing the plugin's own work.
               The count is stated in all three cases: rows disappear from the table while the badge above
               still counts them (cable_count == rows shown + missing), and an operator watching them go
               needs to read how many and why. {% endcomment %}
            {% if missing_state == 'rollback' %}
              <tr><td colspan="3" class="text-muted">{{ missing_cables }} cable(s) of the job no longer exist: this job was rolled back through the plugin, which deletes the cables it created and keeps their ids as its trace. Expected — nothing was deleted behind the plugin's back.</td></tr>
            {% elif missing_state == 'partial' %}
              <tr><td colspan="3" class="text-warning">{{ missing_cables }} cable(s) of the job no longer exist (deleted outside the plugin). A rollback allowed to delete only some of them leaves the very same trace, and the rest of the job's cables are still there — the plugin cannot tell the two apart.</td></tr>
            {% else %}
              <tr><td colspan="3" class="text-warning">{{ missing_cables }} cable(s) of the job no longer exist (deleted outside the plugin). This job is not marked rolled back, so the plugin did not delete them.</td></tr>
            {% endif %}
          {% endif %}
        </tbody>
      </table>
    </div>
  </div>
</div>

{% if channel.racks %}
<div class="row">
  <div class="col col-md-12">
    <div class="card">
      <h2 class="card-header">
        Channel — locate &amp; patch
        {% badge object.get_status_display bg_color=object.get_status_color %}
      </h2>
      <div class="card-body">
        <p class="text-muted small mb-3">
          Per rack of the channel (source→target): the device <strong>highlighted</strong> in its
          native elevation (locate it), and the exact <strong>port to patch</strong> (in red).
          Use <strong>Trace</strong> (above) for the full physical path.
        </p>
        {% include 'netbox_autocabling/inc/channel_racks.html' %}
      </div>
    </div>
  </div>
</div>
{% endif %}
{% endblock %}