Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use DesktopModules/CompanyName/ModuleName folder #28

Open
WillStrohl opened this issue Jun 7, 2019 · 0 comments
Open

Use DesktopModules/CompanyName/ModuleName folder #28

WillStrohl opened this issue Jun 7, 2019 · 0 comments
Labels
enhancement New feature or request sponsors welcome The effort required would make a sponsor the ideal approach to closing this issue.

Comments

@WillStrohl
Copy link
Contributor

Is your feature request related to a problem?

Please describe.
Currently, when you create a new module, it creates it in the root of the DesktopModules folder like below:

DesktopModules/ModuleName

While this is okay, there is a higher possibility for module developers to create and run into naming conflicts with other modules. For example, two modules name SimpleBlog:

DesktopModules/SimpleBlog
and
DesktopModules/SimpleBlog

Describe the solution you'd like

When creating a module, it should instead use the following folder structure:

DesktopModules/CompanyName/ModuleName

This would reduce the potential for naming conflicts. Using the previous example, the resulting conflict no longer occur:

DesktopModules/Acme/SimpleBlog
and
DesktopModules/Zeta/SimpleBlog

Additional context

This should also be done with the Skin Object, since this is installed in the DesktopModules folder as well.

@WillStrohl WillStrohl added the enhancement New feature or request label Jun 7, 2019
@WillStrohl WillStrohl added the sponsors welcome The effort required would make a sponsor the ideal approach to closing this issue. label Aug 30, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request sponsors welcome The effort required would make a sponsor the ideal approach to closing this issue.
Projects
None yet
Development

No branches or pull requests

1 participant