-
Notifications
You must be signed in to change notification settings - Fork 293
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
Please test upcoming version of django-angular 2.0 #322
Comments
I think the documentation about "Running the demo" should mention Also, I think Then, there is 1 failing test and 2 warnings :
|
We could also add the step:
|
Thanks @adrienbrunet |
./manage.py test Creating test database for alias 'default'...
Ran 70 tests in 1.314s FAILED (errors=1) |
OK. Changed the docs to invoke So, @maltitco from your point of view everything is OK for releasing version 2.0? |
@jrief I found first issue And still testing... |
second issue with Ajax button nothing happen. @jrief more bugs I did not find, you will only have to add the information wrote @adrienbrunet to the documentation. |
The first issue is solved. I presume that the second one, is not a real issue. Could you please retry locally and check if you see an error message above. Remember that the combination "John Doe" is rejected. @maltitco Thanks anyway and please retry. |
@maltitco I have found a solution for the second problem, provided it is the problem I assumed. |
@jrief in /model_scope/ form Submit via Ajax don't work: She same is in combined_validation in console TypeError: the JSON object must be str, not 'bytes'
|
@maltitco About File upload
|
On my local:
When it comes to uploading files it was missing npm install ng-file-upload. |
Exciting news from the core maintainer of django-angular:
Version 2.0 is about of being released.
Please help me to review this pull request
https://github.com/jrief/django-angular/tree/releases/2.0.x
and have a look at the site explaining its features interactively:
https://django-angular.awesto.com/model_scope/
The text was updated successfully, but these errors were encountered: