Modify ↓
Ticket #4058 (closed defect: fixed)
Opened 5 years ago
Last modified 5 years ago
Two spaces in a component name causes an error
| Reported by: | recaffeinated john | Owned by: | cboos |
|---|---|---|---|
| Priority: | normal | Milestone: | 0.11 |
| Component: | general | Version: | 0.10 |
| Severity: | minor | Keywords: | component |
| Cc: | |||
| Release Notes: | |||
| API 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
Change History
comment:1 follow-up: ↓ 2 Changed 5 years ago by uh oh
comment:2 in reply to: ↑ 1 Changed 5 years ago by cmlenz
comment:3 Changed 5 years ago by cboos
- Milestone set to 0.11
- Owner changed from jonas to cboos
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 Changed 5 years ago by cboos
#3454 presented another problem related to non-normalized spaces in enum names.
comment:6 Changed 5 years ago by cboos
- Resolution set to fixed
- Status changed from new to closed
Note: See
TracTickets for help on using
tickets.
Can my email address be removed? I thought it would be obfuscated.