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

Package aliasing #731

Closed
moderndeveloperllc opened this issue Apr 30, 2014 · 1 comment
Closed

Package aliasing #731

moderndeveloperllc opened this issue Apr 30, 2014 · 1 comment

Comments

@moderndeveloperllc
Copy link
Contributor

Is there currently a solution for creating a package aliases? For instance, I just put in a pull request for jGrowl. The lib is in the repo as just jgrowl/ when it should probably be jquery.jgrowl/ as indicated by the repo's file names. Suggestions?

@jimaek
Copy link
Member

jimaek commented Apr 30, 2014

Yes, the current name is a legacy issue before we added that rule.
The only solution would be to duplicate the project and name the new one jquery.jgrowl.
Later we can hide the old one from the frontend. But not sure if its worth it.
What do you think?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants