beat.web.team.serializers module¶
-
class
beat.web.team.serializers.BasicTeamSerializer(instance=None, data=<class 'rest_framework.fields.empty'>, **kwargs)[source]¶ Bases:
rest_framework.serializers.ModelSerializerNo name and no members
-
class
beat.web.team.serializers.SimpleTeamSerializer(instance=None, data=<class 'rest_framework.fields.empty'>, **kwargs)[source]¶
-
class
beat.web.team.serializers.FullTeamSerializer(instance=None, data=<class 'rest_framework.fields.empty'>, **kwargs)[source]¶
-
class
beat.web.team.serializers.CreatedTeamSerializer(instance=None, data=<class 'rest_framework.fields.empty'>, **kwargs)[source]¶
-
class
beat.web.team.serializers.UpdatedTeamSerializer(instance=None, data=<class 'rest_framework.fields.empty'>, **kwargs)[source]¶
-
class
beat.web.team.serializers.TeamCreationSerializer(instance=None, data=<class 'rest_framework.fields.empty'>, **kwargs)[source]¶ Bases:
rest_framework.serializers.ModelSerializer-
class
Meta[source]¶ Bases:
object-
model¶ alias of
beat.web.team.models.Team
-
fields= ['name', 'short_description', 'accessibility', 'members']¶
-
-
create(validated_data)[source]¶ We have a bit of extra checking around this in order to provide descriptive messages when something goes wrong, but this method is essentially just:
return ExampleModel.objects.create(**validated_data)
If there are many to many fields present on the instance then they cannot be set until the model is instantiated, in which case the implementation is like so:
example_relationship = validated_data.pop(‘example_relationship’) instance = ExampleModel.objects.create(**validated_data) instance.example_relationship = example_relationship return instance
The default implementation also does not handle nested relationships. If you want to support writable nested relationships you’ll need to write an explicit .create() method.
-
class
-
class
beat.web.team.serializers.TeamUpdateSerializer(instance=None, data=<class 'rest_framework.fields.empty'>, **kwargs)[source]¶