Pass user object to CommentForm (initial data)

[Maciej Wiśniowski]

CommentForm should check if current user is authenticated and if so, initial data for user's 'name' and 'email' should be filled.
Also, it is very useful to have access to at last user object (request?) in form's init. This way you're able to customize it a lot, eg. hide some fields or mark them readonly depending on user.
Proposed patch passes user object to CommentForm and then initial data are populated with 'name' and 'email' from user object

[Thejaswi Puthraya]

Ideally, you shouldn't change the API because Django is committed to
backwards-compatibility. The CommentForm always had access to initial
kwarg that would display the default values.

I have attached a patch that doesn't break compatibility but I somehow
feel that I am violating DRY at
​http://code.djangoproject.com/browser/django/trunk/django/contrib/comments/views/comments.py#L34

Let's see what the core-devs have to tell.

[Thejaswi Puthraya]

git-patch against the latest checkout

[Maciej Wiśniowski]

Patch from thejaswi_puthraya only adds username and e-mail to inital_data while my original idea was also to pass user object to form's init function. This way it is possible to customize form, eg. by hiding some fields for specific users.
Backward compatibility is only broken if one has own comment form with overriden init function that doesn't accept kwargs.

[Thejaswi Puthraya]

Slightly related to #12742

[Thejaswi Puthraya]

Check my comment on https://code.djangoproject.com/ticket/12742#comment:7

[Jacob]

django.contrib.comments has been deprecated and is no longer supported, so I'm closing this ticket. We're encouraging users to transition to a custom solution, or to a hosted solution like Disqus.

The code itself has moved to ​https://github.com/django/django-contrib-comments; if you want to keep using it, you could move this bug over there.