As I mentioned before I would contribute the feature. I have enough experience with python and django :>
Just lmk what I should do.

love and trans solidarity <33

Another thing I noticed was, that if a shop ships to only one country, the API always returns the country name representation of the country, instead of its code. I don't think that is a good design, as you need to first parse it in the back-end, just for the user to make weird string stuff.

This second option would also eliminate the need of maintaining the data any differently.

What I would rather do is return the list of country codes, then parse the plaintext field to the values:

- isWorldwide
- isEurope
- etc..

I think this should be an improvement, as people will do that otherwise in their program and it would eliminate the step. This ofc. can and should be cached.

Ahhh ok that makes sense. My possible solution would be to:

You could expose both fields separately to the API and ofc. document why. This sounds reasonable to maintain, but wouldn't add too much abstraction.

[thread]

Of course I would be open to contributing, if you'd either open source the project, or add me to the project.

~~~I hope I didn't just overlook the repository~~~