Klaas van Schelven 2c4e8b9f20 Regular v.s. Django Testcase: be explicit ...

I recently ran into a funny issue where the TestCases were influencing my
development DB's contents

2024-04-15 09:17:53 +02:00

..

management

Add command to store events

2024-03-30 21:15:39 +01:00

migrations

denormalize/cache last_frame_* and transaction on Event and Issue

2024-04-10 09:12:15 +02:00

templates/events

Remove unused base template

2024-04-05 10:13:56 +02:00

__init__.py

The ugliest thing that could get a stacktrace on screen

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

admin.py

Store calculated type and value on issue and event and use these values in the templates

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

apps.py

Hook make_consistent() into debug_server reloads

2024-03-24 22:08:38 +01:00

factories.py

ingest_order: first setup

2024-04-08 22:13:52 +02:00

models.py

Event already exists: return 400; implement with one less query

2024-04-11 11:03:41 +02:00

tests.py

Regular v.s. Django Testcase: be explicit

2024-04-15 09:17:53 +02:00

urls.py

Add 'plain' view (Python-specific; only half-tested)

2024-03-30 23:10:18 +01:00

views.py

Add 'plain' view (Python-specific; only half-tested)

2024-03-30 23:10:18 +01:00