Goksel Coban

@michaldyczko Can you please share the problem (which part of the code causes this problem) and your solution?

Overriding/updating `prepare_value` method of the field may solve this issue. ```python class QuillFormField(forms.fields.JSONField): ... def prepare_value(self, value): return value.json_string ``` ```python class QuillFormField(forms.fields.JSONField): ... def prepare_value(self, value): if hasattr(value, "json_string"):...

I guess, the issue is resolved.

@ericel @faaizajaz @LeeHanYeong You can use this kind of helper function for plain text inputs. ```python def get_quill(value): quill = Quill({ 'html': '%s' % value, 'delta': { "ops": [ {"insert":...

Hi, thank you for reporting this. As far as I see, you debugged the problem. Can you open a PR to fix this problem?

Hi, thank you for reporting this. > If I send { img: null } it throws This field may not be null error during validation. Do you get the same...

AFAIK, there is no solution for this right now. It needs to be improved. If you are using `drf-spectacular`, `PolymorphicProxySerializer` may help. It allows you to show different serializers depending...

Hi, thank you for these fields. Sorry, but I couldn't understand the use case of these fields. In these cases, I think we should we Django forms instead of DRF....

Yes, I agree `apan` should be fixed. What do you think about comparing transaction ids in `__eq__`?

> Checking the txid in the object's __eq__ method seems a little unpythonic to me, personally. I see, It may make sense when you think that these are two python...