Modify ↓
Opened 18 years ago
Closed 18 years ago
#4058 closed defect (fixed)
Two spaces in a component name causes an error
| Reported by: | recaffeinated john | Owned by: | Christian Boos |
|---|---|---|---|
| Priority: | normal | Milestone: | 0.11 |
| Component: | general | Version: | 0.10 |
| Severity: | minor | Keywords: | component |
| Cc: | Branch: | ||
| Release Notes: | |||
| API Changes: | |||
| Internal Changes: | |||
Description
After naming a component "Test - General" (notice two spaces after Test) the ticket system wouldn't allow me to assign a ticket to that component. Instead, I received an
error: "Test - General" is not a valid value for the component field.
Attachments (0)
Change History (6)
follow-up: 2 comment:1 by , 18 years ago
comment:2 by , 18 years ago
comment:3 by , 18 years ago
| Milestone: | → 0.11 |
|---|---|
| Owner: | changed from to |
Same issue for milestones (#4142) and probably everything that ends up being put in a <select>. As I don't think there's a good reason to try to preserve the actual number of spaces, we should normalize spaces, i.e. instead of just name.strip(), do ' '.join(name.split()).
comment:4 by , 18 years ago
#3454 presented another problem related to non-normalized spaces in enum names.
comment:6 by , 18 years ago
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
Note:
See TracTickets
for help on using tickets.
Can my email address be removed? I thought it would be obfuscated.