Merge lp:~stevenk/launchpad/better-name-field into lp:launchpad
Proposed by
Steve Kowalik
Status: | Merged |
---|---|
Approved by: | Curtis Hovey |
Approved revision: | no longer in the source branch. |
Merged at revision: | 14816 |
Proposed branch: | lp:~stevenk/launchpad/better-name-field |
Merge into: | lp:launchpad |
Diff against target: |
314 lines (+52/-76) 10 files modified
lib/lp/registry/browser/team.py (+9/-3) lib/lp/registry/browser/tests/private-team-creation-views.txt (+2/-1) lib/lp/registry/browser/tests/test_team.py (+16/-0) lib/lp/registry/interfaces/person.py (+0/-3) lib/lp/registry/model/person.py (+6/-7) lib/lp/registry/templates/people-newteam.pt (+0/-1) lib/lp/registry/templates/person-macros.pt (+0/-36) lib/lp/registry/templates/team-edit.pt (+0/-5) lib/lp/registry/tests/test_person.py (+14/-17) lib/lp/services/fields/__init__.py (+5/-3) |
To merge this branch: | bzr merge lp:~stevenk/launchpad/better-name-field |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Ian Booth (community) | Approve | ||
Curtis Hovey (community) | code | Approve | |
Review via email: mp+93317@code.launchpad.net |
Commit message
[r=sinzui,
Description of the change
Firstly, slightly change the blacklisted message, and remove some duplication.
Also re-order the visibility field after we re-add it to the form if the user is permitted to set it.
Remove the JS that was adding private- to the name field when the visibility was changed.
To post a comment you must log in.
"Please contact Launchpad Support." might be lacking and we strive to avoid "please". Maybe
Contact Launchpad Support if you want to use this name.
Your hack is ugly, but two lines. You can consider using the zope way o selecting field name to change the order:
field. __name_ _ for field in self.form_fields
field_ names.insert( 2, 'visibility')
self.form_ fields = self.form_ fields. select( field_names)
field_names = [
if field.__name__ =! 'visibility']