Klaas van Schelven 8d17e7b128 For log messages, demote the msg into the value ...

and make the type 'Log Message'.
This may just be a matter of personal taste, but I've always found these
messages-as-type super-confusing. I'd rather have some made up (but clear,
and thanks to the whitespace unlikely-to-otherwise-exist) type "Log Message".

This is also inline in what I've already done in the UI.

2024-04-08 14:48:39 +02:00

..

migrations

Introduce 'Grouping' data-modeling

2024-04-08 11:41:15 +02:00

templates/issues

'No info available' for breadcrumbs

2024-04-05 09:10:33 +02:00

__init__.py

The ugliest thing that could get a stacktrace on screen

2023-11-04 21:02:04 +01:00

admin.py

Introduce 'Grouping' data-modeling

2024-04-08 11:41:15 +02:00

apps.py

The ugliest thing that could get a stacktrace on screen

2023-11-04 21:02:04 +01:00

factories.py

Introduce 'Grouping' data-modeling

2024-04-08 11:41:15 +02:00

models.py

Introduce 'Grouping' data-modeling

2024-04-08 11:41:15 +02:00

regressions.py

Implement unmute-after-time

2024-03-08 20:53:31 +01:00

tests.py

For log messages, demote the msg into the value

2024-04-08 14:48:39 +02:00

urls.py

Breadcrumbs, at least implement _something_

2024-03-31 23:04:15 +02:00

utils.py

Factor out the idea (exception -> type_, value) what we have

2024-04-08 14:39:14 +02:00

views.py

details page: show relevant info, in a non-fugly way

2024-04-04 13:30:19 +02:00