Please help us testing the upcoming release 0.8.0.
From a functional point of view, nothing changed between 0.7.16 and 0.8.0 with one big exception:
djangular has been renamed to djng. This was requested by many users since it
a) caused a naming conflict with another Django app named the same and
b) the identifier "djangular" by many users was seen as a bad choice for this Django app.
Please read jrief#35 for the preceded discussion on this topic.
- Ready for Django-1.9.
- Fixed: Non-ascii characters were not being processed correctly by
django.http.request.QueryDict.init. - In JavaScript, replaced
console.logby$log.log. - Use decimal base on invocation of
parseInt. - Use square brackets to access scope members, which otherwise won't support fields containing
-. - templatetag
load_djng_urlshas been removed. - For CRUD, check if request method is allowed.
- Fixed djngError directive, when using AngularJS-1.3.
- Added support for
ngMessages, as available with AngularJS-1.3.
Demo on how to combine Django with Angular's form validation.
Detailed documentation on ReadTheDocs.
Please participate at this survey on naming conventions!
Please drop me a line, if and where you use this project.
- Seamless integration of Django forms with AngularJS controllers.
- Client side form validation for Django forms using AngularJS.
- Let an AngularJS controller call methods in a Django view - kind of Javascript RPCs.
- Manage Django URLs for static controller files.
- Three way data binding to connect AngularJS models with a server side message queue.
- Perform basic CRUD operations.
Copyright © 2015 Jacob Rief.
MIT licensed.