Defect #6253
closed
Allowing dot in project identifier
Added by Ehsan Afzali over 14 years ago.
Updated about 14 years ago.
Description
I wanted to know why is dot restricted in project identifier field. Here in our company we use dot syntax for our projects identification and repository names and because your auto repository creation uses project identifier as repository name, it becomes an issue for us.
I think dot should be allowed. Anyone have a reason why allowing dot could be bad?
- Assignee set to Eric Davis
I think no one has any reason! Could please handle this Eric? theres no activies on this issue about a month.
Eric Davis wrote:
Anyone have a reason why allowing dot could be bad?
I can think of nothing.
- Status changed from New to Closed
- Assignee deleted (
Eric Davis)
- Resolution set to Wont fix
Sorry, it turns out this won't work due to the routing. Example, identifier - "test.123" gets this error:
ActionController::RoutingError (No route matches "/projects/settings/test.123" with {:method=>:get}):
123 is being used as the format option, which is invalid.
- Status changed from Closed to Reopened
- Assignee set to Eric Davis
- Status changed from Reopened to Closed
- Assignee deleted (
Eric Davis)
Ehsan Afzali wrote:
This how you handle the repository explorer because the folders in repository may contains dot
The repository view is different than the projects because projects uses the format option as part of it's rest API (format = xml for "project.xml). If someone wants to submit a patch for this that includes full integration tests for browsing projects with a dot identifier (including different formats for the REST API), then we can see about including it.
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by 
Updated by Toshi MARUYAMA