Opened 11 years ago
Closed 11 years ago
#22195 closed Cleanup/optimization (fixed)
Use constants to define built-in tags
Reported by: | Russell Keith-Magee | Owned by: | Tomáš Ehrlich |
---|---|---|---|
Component: | Core (System checks) | Version: | 1.7-alpha-1 |
Severity: | Normal | Keywords: | |
Cc: | Tim Martin, tomas.ehrlich@… | Triage Stage: | Accepted |
Has patch: | yes | Needs documentation: | no |
Needs tests: | no | Patch needs improvement: | no |
Easy pickings: | yes | UI/UX: | no |
Description
Via discussion on django-developers:
The code for system checks currently uses freeform strings to register against tags (e.g., @register('compatibility')
).
This is potentially prone to error, since you can easily mistype the string, and then the check won't get caught by the tag.
Internally, we should be using constants for built-in tags.
Attachments (1)
Change History (4)
comment:1 by , 11 years ago
Cc: | added |
---|
by , 11 years ago
Attachment: | check-constants.diff added |
---|
comment:2 by , 11 years ago
Cc: | added |
---|---|
Has patch: | set |
Owner: | changed from | to
Status: | new → assigned |
comment:3 by , 11 years ago
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
Note:
See TracTickets
for help on using tickets.
Added constants for check tags.