agateblue / agateblue/django-dynamic-preferences

ModelChoicePreference when pk not exists

Open
#314 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
Python
Stars
359
Forks
86
PR merge metrics
No merged PRs in 30d

Description

Hi,

When I use the `ModelChoicePreference` preference I save the pk of an object. If this object is deleted, the serializer's behavior is to throw an exception. Wouldn't the correct thing be to return empty in this case?

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.