mirror of
https://github.com/jlengrand/bugsink.git
synced 2026-03-10 08:01:17 +00:00
3bab02fda2
grouping will return later as Issue.grouping_keys & Event.grouping_key i.e. with the relevant info directly resolved See #146
36 lines
1.3 KiB
Python
36 lines
1.3 KiB
Python
from rest_framework import serializers
|
|
|
|
from .models import Issue
|
|
|
|
|
|
class IssueSerializer(serializers.ModelSerializer):
|
|
class Meta:
|
|
model = Issue
|
|
|
|
# TODO better wording:
|
|
# This is the first attempt at getting the list of fields right. My belief is: this is a nice minimal list.
|
|
# it _does_ contain `data`, which is typically quite "fat", but I'd say that's the most useful field to have.
|
|
# and when you're actually in the business of looking at a specific event, you want to see the data.
|
|
fields = [
|
|
"id",
|
|
"project",
|
|
"is_deleted",
|
|
"digest_order",
|
|
"last_seen",
|
|
"first_seen",
|
|
"digested_event_count",
|
|
"stored_event_count",
|
|
"calculated_type",
|
|
"calculated_value",
|
|
"transaction",
|
|
# "last_frame_filename",
|
|
# "last_frame_module",
|
|
# "last_frame_function",
|
|
"is_resolved",
|
|
"is_resolved_by_next_release",
|
|
# "fixed_at", too "raw"? i.e. too implementation-tied?
|
|
# "events_at", too "raw"? i.e. too implementation-tied?
|
|
"is_muted",
|
|
# "unmute_on_volume_based_conditions", too "raw"? i.e. too implementation-tied?
|
|
]
|