-
Notifications
You must be signed in to change notification settings - Fork 290
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
Namespace conflict with djangular #11
Comments
Good point, but what are the options? However, I don't get the intention of djangular. It's a kind of wizard, to start projects using AngularJS. Its intention is to unload the responsibility from server-side rendering to the client, whereas the intention of my module is, to keep that in Django. In former projects, I made bad experience trying to let the client do to much of the "dirty" work, so I switched back to server side modeling/rendering/validation. Always think about Kindle users. My proposal: If there are features in djangular you really like, tell me, and if they make sense, I will implement them in django-angular, doing them my way. Jacob |
How about "angular-dj'? |
Declined. Module names may not contain dashes, and btw. I don't like it. |
This feature in Django 1.7 should help resolve this without renaming anything: The one thing I use djangular for is getting access to the settings variables (so I can point angular at the right urls etc). That being said, #35 is all about renaming...so....is not renaming still an issue? |
There is another module which uses the same package namespace
djangular
:https://github.com/appliedsec/djangular
This is rather unpleasant as it disallows to install both packages at the same time.
The text was updated successfully, but these errors were encountered: