I think this behavior is good. Module names should refer to a file/directory as is, without being transformed by Agavi beforehand, so that it would behave consistently across all operating systems.
AFAIK, Mac OS X _preserves_ the case, although case-sensitivity is optional*. Just treat your Mac as case-sensitive and you'll be fine. [ simon.cpu ] * You can create case-sensitive HFS+ volumes, although many apps would no longer run. On Sat, Oct 24, 2009 at 7:38 PM, Michal Charemza <[email protected]> wrote: > Hi, > > I recently found an issue when moving a project over from Mac to > Linux. I found if I create a module > > "Admin" > > Then on a Mac using the > > AgaviContext::getModel > > method works using both "admin" and "Admin", but fails on linux: I'm > assuming this is due to the fact that Mac has a case insensitive file > system...? > > Also, when creating an action using "agavi action-create" and entering > "admin", the script works fine with no error, but the lower case > "admin" is used in paths / class names (and the class names do then > fail on Mac). I wonder if these issues should be fixed somehow...? > > Michal. > > _______________________________________________ > users mailing list > [email protected] > http://lists.agavi.org/mailman/listinfo/users > _______________________________________________ users mailing list [email protected] http://lists.agavi.org/mailman/listinfo/users
