-
Notifications
You must be signed in to change notification settings - Fork 1
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
Tests fail on new project - can't reverse "javascript-catalog" - have proposed fix #92
Comments
Django version 2.2.3.0, javascript_catalog does exist if I import it from django within the virtualenv. I'm a python dev but not a django dev so I'm not great at debugging this
|
I suspect the problem is something related to this line in the recent django update patch - https://github.com/liqd/a4-cookiecutter/pull/90/files#diff-521ab0577f937972db3f4fa5f0c0ec06L74 |
If I replace line 74 in urls.py with
Then the tests pass and the page renders. I'd make a pull request with that 'fix' but I'm too new to this project and django to understand the implications of this. Even with this line though, the page looks weird- like broken JS, so this may not be the full answer. |
@mcscope thanks a lot for the issue and also for the solution. It is fixed. |
edit: I have a proposed fix to this - see my final comment
Following the setup guide on a first install, I'm getting test failures.
I did the cookiecutter fetch step, then
make install
thenmake tests
- I believe I have all relevant dependencies and no errors on the first two steps beforemake test
. I have both python 3.7 and python 2.7 installed, looks like this is using 3.7, it's in all the paths.E django.urls.exceptions.NoReverseMatch: Reverse for 'javascript-catalog' not found. 'javascript-catalog' is not a valid view function or pattern name.
There are 32 failures
================== 32 failed, 156 passed, 70 warnings in 105.55 seconds ===================
Here's one of the failing tests in its entirety
Here are the only references to javascript catalog in the folder -
The text was updated successfully, but these errors were encountered: