We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
According to the current implementation, if we install to plugins with the same name but different developer they will overwrite each other.
What should be done about this ?
The text was updated successfully, but these errors were encountered:
then we will have to write our own registry to prevent duplicates which will force developer to rename their plugin as we use npm implicitly .
Sorry, something went wrong.
the npm strategy seems more appealing to me, but don't know if it's the best ?!
npm
we can try. i will modify the code a bit but it will have the same functionality. should i proceed?
Yes, please proceed.
On Fri, Dec 4, 2015 at 11:49 PM, Yusuf Mohamed [email protected] wrote:
we can try. i will modify the code a bit but it will have the same functionality. should i proceed? — Reply to this email directly or view it on GitHub #5 (comment).
— Reply to this email directly or view it on GitHub #5 (comment).
Sameh Kamaleldin
YusufMohamed
No branches or pull requests
According to the current implementation, if we install to plugins with the same name but different developer they will overwrite each other.
What should be done about this ?
The text was updated successfully, but these errors were encountered: