Add additional validation to bug tracker URLs
Review Request #3378 — Created Sept. 29, 2012 and submitted
When specifying a custom bug tracker URL, the URL is passed through additional validation to ensure that there is a '%s' string formatting element.
Tested on local development server against custom urls and a new GitHub repository's issue tracker. Added unit test for validator.
| Description | From | Last Updated |
|---|---|---|
|
We tend to do a lot of stuff alphabetically, so these should be imported in this order: validate_bug_tracker, validate_review_groups, validate_users. |
 mike_conley
|
|
|
Would love some input on the message. |
KA Karl-L | |
|
As before, we tend to do things alphabetically - so django.forms stuff should be imported before django.http stuff. |
mike_conley
|
|
|
There should be a docstring here say what this test is doing. |
mike_conley
|
|
|
Input on the message here would be appreciated too. |
KA Karl-L | |
|
reviewboard.site isn't the right place for validate_bug_tracker. Can you move it to reviewboard/admin/validation.py (which doesn't exist yet) and move the … |
 david
|
-
Hey Karl, This looks really good! Just a few suggestions - see below. -Mike
-
We tend to do a lot of stuff alphabetically, so these should be imported in this order: validate_bug_tracker, validate_review_groups, validate_users.
-
How about "The path should resemble: http://www.example.com/issues?id=%s where %s will be the bug number.
-
As before, we tend to do things alphabetically - so django.forms stuff should be imported before django.http stuff.
-
-
KA
- Change Summary:
-
Fixed a few import ordering issues (made alphabetical), updated some copy and fixed test so that it can fail (instead of just error).
