Re: Better form fields for django.contrib.postgres.fields

2016-05-24 Thread Paul Martin
*OK thanks for the replies. The first enhancement would be a change in how choices are handled for the ArrayField. With this change,* *choices would be based on the base field. If choices keyword argument is given, a multiple choice field is used and the array value will be composed* *of thes

Re: Better form fields for django.contrib.postgres.fields

2016-05-23 Thread Tim Graham
A couple suggestions: It'd be better to propose each enhancement separately (and on this mailing list, rather than in Trac) rather than combining them into one ticket. It's not obvious to me that all the proposed features which mainly involve forms should be declared at the model level. I guess

Re: Better form fields for django.contrib.postgres.fields

2016-05-23 Thread Asif Saifuddin
Hi, The first step is the ticket need to be accepted and then push the change as pull request on master branch. Thanks On Monday, May 23, 2016 at 6:56:43 PM UTC+6, Paul Martin wrote: > > Hi, > > This is my first time contributing to Django. It's a lot of different > features in one to improve

Better form fields for django.contrib.postgres.fields

2016-05-23 Thread Paul Martin
Hi, This is my first time contributing to Django. It's a lot of different features in one to improve how form fields are produced for ArrayField, HStoreField and JSON FIeld. I opened a ticket here with more details and a screenshot of the admin for a sample model. https://code.djangoproject.c