-
-
Notifications
You must be signed in to change notification settings - Fork 137
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
Make Menu.get_template neutral to template engine #190
Make Menu.get_template neutral to template engine #190
Conversation
There is change in internal API: The `Menu.get_template()` now return the instance of Template class in `django.template.backends`, not `django.template.base.Template` class.
Hi @hongquan, Thank you for this. It looks as though the Travis CI integration hasn't worked for this PR (I'm unsure why). Would you possibly be able to make a very minimal commit, and we'll see if Travis CI will do it's thing? |
I've just added 1 commit. |
Hi @hongquan, Travis CI is failing to build with a 'Abuse detected' message for some reason. I've just opened a ticket with their support team to see why this is happening. |
Hi @hongquan, I have the following feedback from the Travis team:
Are you okay to try signing up for an account on travis-ci.org using you github account? It sounds like that might solve the problem. Thanks :) |
Thanks @hongquan. If you could just make another small commit, we'll see if it worked :) maybe just change your name in contributors, then commit a fix for it after? |
Codecov Report
@@ Coverage Diff @@
## master #190 +/- ##
==========================================
- Coverage 97.08% 97.01% -0.08%
==========================================
Files 73 73
Lines 2644 2644
==========================================
- Hits 2567 2565 -2
- Misses 77 79 +2
Continue to review full report at Codecov.
|
Hi @hongquan, Thank you for your time in putting this together. I'm happy enough with the code changes here, but I'm not quite sure about making these additions to the documentation just yet - I think I would rather those be added separately as another pull, along with some other things, such as:
The instructions can then be simplified, and we'll have a working settings configuration that we can point developers to in case they'd rather look at / copy from a working implementation. Does this sound okay to you? |
It is OK to me. Do I need to revert the commit of updating documentation? |
@hongquan Yes, if you wouldn't mind :) |
@@ -7,3 +7,4 @@ Rendering menus | |||
|
|||
template_tag_reference | |||
custom_templates | |||
use_with_jinja2 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please remove this for now - We'll work on Jinja-specific stuff as a separate piece of work :)
{{ main_menu() }} | ||
</div> | ||
|
||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please remove this file for now - We'll work on Jinja-specific stuff as a separate piece of work :)
This reverts commit 40a5b83.
I removed the docs. |
Big thanks @hongquan :) This has now been merged |
This is to make wagtailmenus work with Jinja2 template engine (#89).
The PR makes change in one internal API: The
Menu.get_template()
now return instance ofTemplate
class indjango.template.backends
, notdjango.template.base.Template
class.