From 02a29a90299c7b3ce14a76af58f99c615ec12437 Mon Sep 17 00:00:00 2001
From: Klaas van Schelven <klaas@vanschelven.com>
Date: Mon, 1 Apr 2024 22:39:03 +0200
Subject: [PATCH] More pieces of info for the details page

---
 issues/templates/issues/issue_event_details.html | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/issues/templates/issues/issue_event_details.html b/issues/templates/issues/issue_event_details.html
index 56ca250..36eb319 100644
--- a/issues/templates/issues/issue_event_details.html
+++ b/issues/templates/issues/issue_event_details.html
@@ -5,6 +5,7 @@
 {% block tab_content %}
 
 <div>User: {{ parsed_data.user }}</div>
+<div>Runtime: {{ parsed_data.contexts.runtime.name}}</div> {# sentry gives this prime location (even a picture)... but why... it's kinda obvious what you're working in right? Maybe I could put it at the top of the modules list instead. And check if there's any other relevant info in that runtime context (RTFM) #}
 
 {% if parsed_data.logentry %}
 
@@ -33,6 +34,7 @@
             {% endfor %}
 
             <h3 class="text-2xl mt-4">Request headers</h1>
+            {# TODO the user's browser and OS can be deduced from the request headers. Perhaps that info should go near the headers #}
 
             {% for header_key, header_value in parsed_data.request.headers.items %}
             <div class="flex">