Redmine

Arnaud GUT wrote:

I was wondering if the project identifier constraint could be relaxed a bit and accept both upper and lower case letters ?

That seems reasonable.

BTW: there might be a small bug in the automatic identifier generation at project creation time, where underscores becomes dashes instead of staying as underscores.

Fixed in r11195. Thanks for pointing this out.

When this could be implemented as it seems to not be a huge modification (a priori !)?
If you prefer, answer on my private mail.

This shouldn't be difficult to implement:

root/trunk/public/javascripts/project_identifier.js | line 54:

-  identifier = identifier.replace(/[^a-z0-9_]+/gi, '-'); // remaining non-alphanumeric => hyphen
+  identifier = identifier.replace(/[^a-zA-Z0-9_]+/gi, '-'); // remaining non-alphanumeric => hyphen

Note: I don't know if/how this change might affect other components.

What is the use case behind this? What benefit do you get from uppercase identifiers and uppercase URL's? Mostly this makes more problems than uses?

How do you plan to handle Identifieres like "Redmine", "redmine" and "RedMine"? They could occur, but the url is in this cases case insensitive.

The use case was one where we would synchronize a repository hierarchy (a Hg repository managed by RhodeCode to be more precise) with a project hierarchy within Redmine. On the repository side, the URLs are built to map the filesystem which is case sensitive under Unix. Once the names were flatten as lowercase Redmine-project-IDs it became impossible to reverse-map those IDs to proper repository paths.

We (Arnaud and I) don't rely on this use case anymore, this ticket may be closed as far as I'm concerned.