[Django] #31519: Unclosed tags don't cause Syntax errors in Templates

5 views
Skip to first unread message

Django

unread,
Apr 27, 2020, 8:34:55 AM4/27/20
to django-...@googlegroups.com
#31519: Unclosed tags don't cause Syntax errors in Templates
-------------------------------------------+------------------------
Reporter: Bithive | Owner: nobody
Type: Uncategorized | Status: new
Component: Template system | Version: 3.0
Severity: Normal | Keywords: Tags
Triage Stage: Unreviewed | Has patch: 0
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 0
UI/UX: 0 |
-------------------------------------------+------------------------
Unclosed Tags e.g. "{% extends '_base" don't trow syntax errors.

These problems are hard to detect via tests maybe Django should throw a
syntax error

--
Ticket URL: <https://code.djangoproject.com/ticket/31519>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.

Django

unread,
Apr 27, 2020, 2:59:06 PM4/27/20
to django-...@googlegroups.com
#31519: Unclosed tags don't cause syntax errors in templates.
---------------------------------+--------------------------------------
Reporter: Bithive | Owner: nobody
Type: New feature | Status: closed

Component: Template system | Version: 3.0
Severity: Normal | Resolution: wontfix

Keywords: Tags | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
---------------------------------+--------------------------------------
Changes (by felixxm):

* status: new => closed
* type: Uncategorized => New feature
* resolution: => wontfix


Comment:

Thanks for this ticket, however
[https://docs.djangoproject.com/en/3.0/ref/templates/language/#the-django-
template-language DTL] parses only properly closed tags: ''"Django's
template parser looks for the first occurrence of `%}` after a `{%`..."''
and I think we shouldn't change this.

--
Ticket URL: <https://code.djangoproject.com/ticket/31519#comment:1>

Reply all
Reply to author
Forward
0 new messages