-
Notifications
You must be signed in to change notification settings - Fork 95
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
TimeZoneSerializerField not accepting choices argument #69
Comments
This is how I do it now. Maybe this could be incorporated into this package. It now shows a list of all possible timezone fields in the browsable API and in the in an OPTIONS request. |
Agreed it would be great to respond to an @gabn88 would it be possible to expand the field class you have there to accept an optional I think if that was added to this implementation, and then also some basic tests, we could merge it in named something like |
@gabn88 How are you dealing with this now? As far as I've seen, there is no .default_choices anymore. Or do you stick with an old version? |
@normic I use it like this
|
And as a result, the OPTIONS request does not show all the possible choices in the API.
This is related to #61
In my opinion, this should be the first step.
The text was updated successfully, but these errors were encountered: