Include serializers for usage inside rest framework about django-address HOT 2 CLOSED

Hi @devidw! Thanks for the suggestion, it's very much appreciated.

While it's certainly tempting to include things like DRF serializers (and possibly viewsets), I believe it falls outside the responsibility of Django Address. It makes the assumption that users of Django Address are using DRF and not some other API framework (for example, Graphene, or Strawberry). We could potentially be adding dependencies to packages that are of no concern or use to consumers of Django Address (someone using Strawberry GraphQL is unlikely to want to install DRF).

Creating serializers for models in DRF is pretty easy, as you've shown in your issue above; I think it's reasonable to leave defining API interfaces to consumers of Django Address.

from django-address.

@furious-luke Mhm yeah actually true, sounds understandable. Thanks for taking the time and pointing this out. 🙌

from django-address.