-
Notifications
You must be signed in to change notification settings - Fork 3.2k
Closed
Labels
Description
Describe the bug
The following generator classes use naming conventions that are inconsistent with the rest of the generators and with the relationship between other generators and their file names:
"What the name would be if consistent with the rest of the generators" => "What the name actually is"
{
"FullmetalAlchemist" => "Fma",
"Dnd" => "DnD",
"Music::Show" => "Show", # All other other intermediate namespace classes contract to the excluded orphan with a pluralisation where the namespace class starts with the orphan, eg "Book" and "Books". In this case the orphan class appears to be "Musicals" not "Shows", which would modify the relationship but retain consistency (from namespace starts with orphan to either starts with the other).
"Nhs" => "NationalHealthService",
"IdNum" => "IDNum", # I couldn't find an inflector to handle this kind of ID case.
"InternetHttp" => "Internet::HTTP", # This is an exception both for its namespace (Internet, which is all in the default namespace) and its directory location (Default, where other generator classes are not further namespaced)
"TheItCrowd" => "TheITCrowd",
"::Room" => "::TheRoom"
}
Additionally, Locations appears to be a real namespace looking at the directory structure, but isn't one, housing a single generator class (Australia) and contracting as though it was in the default directory. The default directory acting as an extension of the top level namespace seems perfectly reasonable though.
Expected behavior
Generators should use consistent naming and namespace rules to avoid needing arbitrary filtering rules for their randomised or programmatic invocation.
stefannibrasil