route and frontName settings

[MasyH]

Could you add a "route" setting that would override the use of the lowercased modulename, and a "frontName" setting that would allow independence with the route value ? Thank you !

[tzyganu]

@MasyH Evem if this looks like a good(-ish) idea. I will not add it to the module. And here is why. Changing the frontName of a module can be easily done just by editing in config.xml the value of the frontName. Making it configurable will require some amount of code for validating the route name (so it won't conflict with other) and the added value of this is not that big. You can change it to whatever you want after creating and installing the module.

But I won't dismiss this completely. I will implement it when there is nothing else to do for the module. For sure it will not be in the first release. Thanks for the idea. I will leave this open for now but with low priority.

[MasyH]

Thank you for your response ! Yes, it's easy to change the frontName, and
yes it would not be that easy to validate the frontName conflicts.
Now, the other suggestion was to be able to configure the route, using it
in place of the lowercased modulename. This is by far NOT easy to change
after the module has been generated !
Suppose I already have a community module Xyz_Modulename and want to ceate
a local Abc_Modulename... So, I think that yes, the configurable frontName
is nice to have, but a configurable route name taking place of the
lowercased modulename would be a useful feature ! And the validating code
would be similar to the existing one. Thus not so "nice to have", and
probably easier to implement...
That said, I want to say that I discovered and tried UMC some days ago: it
is a wondeful module !!!! Thank you very much for that !

On Fri, Feb 14, 2014 at 1:09 PM, Marius notifications@github.com wrote:

@MasyH https://github.com/MasyH Evem if this looks like a good(-ish)
idea. I will not add it to the module. And here is why. Changing the
frontName of a module can be easily done just by editing in config.xmlthe value of the frontName. Making it configurable will require some amount
of code for validating the route name (so it won't conflict with other) and
the added value of this is not that big. You can change it to whatever you
want after creating and installing the module.

But I won't dismiss this completely. I will implement it when there is
nothing else to do for the module. For sure it will not be in the first
release. Thanks for the idea. I will leave this open for now but with low
priority.

Reply to this email directly or view it on GitHubhttps://github.com//issues/4#issuecomment-35078196
.

[MasyH]

P.S. To be precise, the suggestion is not to just have the requests
rerouted, but to have ALL the module resources using the route name where
the lowercased modulename is used... thus, it would appear in folder names, etc etc.

And It does not always depend on you to decide the module naming conventions...

On Fri, Feb 14, 2014 at 1:25 PM, Hugues Masy hugues.masy@gmail.com wrote:

Thank you for your response ! Yes, it's easy to change the frontName, and
yes it would not be that easy to validate the frontName conflicts.
Now, the other suggestion was to be able to configure the route, using it
in place of the lowercased modulename. This is by far NOT easy to change
after the module has been generated !
Suppose I already have a community module Xyz_Modulename and want to ceate
a local Abc_Modulename... So, I think that yes, the configurable frontName
is nice to have, but a configurable route name taking place of the
lowercased modulename would be a useful feature ! And the validating code
would be similar to the existing one. Thus not so "nice to have", and
probably easier to implement...
That said, I want to say that I discovered and tried UMC some days ago: it
is a wondeful module !!!! Thank you very much for that !

On Fri, Feb 14, 2014 at 1:09 PM, Marius notifications@github.com wrote:

@MasyH https://github.com/MasyH Evem if this looks like a good(-ish)
idea. I will not add it to the module. And here is why. Changing the
frontName of a module can be easily done just by editing in config.xmlthe value of the frontName. Making it configurable will require some amount
of code for validating the route name (so it won't conflict with other) and
the added value of this is not that big. You can change it to whatever you
want after creating and installing the module.

But I won't dismiss this completely. I will implement it when there is
nothing else to do for the module. For sure it will not be in the first
release. Thanks for the idea. I will leave this open for now but with low
priority.

Reply to this email directly or view it on GitHubhttps://github.com//issues/4#issuecomment-35078196
.

[tzyganu]

@MasyH I understood that you want all the module resources to use the route name.
But I wan't to mention that there is already a restriction. If you have a module called Xyz_Modulename installed you won't be able tor create a module Abc_Modulename. I plan to remove this restriction by changing the models (and blocks and helpers) aliases from module/something to namespace_module/something. Then you won't have any conflicts for class names. I will do that as soon as I have everything else working. Then, for sure I will need a way to check for routes conflicts and I may be forced to implement what you are suggesting. But like I said...Not in the first release. Feel free to create a pull request if you can. I'm working on this all by myself (PM, developer, tester). I could really use an additional set of hands and a brain on this.

[tzyganu]

This should be fixed in version 1.9-dev8. You can review it and tell me if it's what you've hoped it will be.