convert DRF ChoiceField to Enum

[zbyte64]

This is to resolve #517 so that we use choices defined from DRF.

This also impacts FilePathField as it is technically a ChoiceField.

[coveralls]

Coverage increased (+0.06%) to 92.779% when pulling 0050f8f on zbyte64:drf-choices into b0cba39 on graphql-python:master.

[zbyte64]

Tests do pass, but can't directly trigger a rebuild. For some reason the CI broke (seems rarely intermittent):

$ curl -sSf -o python-3.5.tar.bz2 ${archive_url}
curl: (56) SSL read: error:00000000:lib(0):func(0):reason(0), errno 104
Unable to download 3.5 archive. The archive may not exist. Please consider a different version.

[cowlicks]

I hit this issue today. Is there a workaround you would recommend that will allow me to have a schema where enums are used for Django choice fields when using the serializer mutation?

[cowlicks]

Ideally, there would be a way to override the defaults for the inputs and outputs.

[PeterDekkers]

@zbyte64 any chance this PR can be resurrected?

I'm using the workaround from #517. It would be great to have a built-in solution.

[zbyte64]

@cowlicks you can always redefine the field where you define your own DjangoObjectType

[zbyte64]

PR now converts multiple choices fields to list of enums.

Now the remaining question is whether it makes sense for FilePathField to be an enum. Choices may not be static as new directories could be added.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[jkimbo]

@zbyte64 is this still a PR that you would like to see merged?

[zbyte64]

This is still an issue and I still believe this is a valid way to address the issue. So yes, we should merge it...

[jkimbo]

Merging this PR because it's been waiting around for ages.

[overide]

@zbyte64 Can you direct me to the example where I see this change in action? I tried it but didn't work, maybe I didn't understand it correctly. I'm using v2.5.0