Misleading text in "constraint not satisfied error" when registering a spec in spec tracker.
Bug #3358 reported by
Sivan Greenberg
This bug report is a duplicate of:
Bug #3186: New spec form has undescribed no-capitals constraint.
Edit
Remove
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Launchpad itself |
New
|
Medium
|
Unassigned | ||
Bug Description
When I first set foot to register a specification in the specification tracker, I figured it would be ok to use the wiki name under which it is available there. spec name(s) (as a launchapd components?). When trying to submit I got:
"May contain letters, numbers, and dashes only. Examples: mozilla-
Prefixed with a "Constraint not satisfied" error.
Although the examples are somewhat clear, it doesn't specify if you're allowed to have mixed lower case and upper case charachters. Apparently, the message should have been:
"Please use *only* lowered case letters, numbers and dashes." since, this is the real constraint it seems to follow.
Revision history for this message
| Matthew Paul Thomas (mpt) wrote | #1 |
To post a comment you must log in.
Ugh. Since specs are likely to be on a wiki, we should allow the wiki's spec name (InterCaps and all) to be used as Launchpad's name. Furthermore, that should be the default value if available.