[Django] #21591: get_messages is not covered in the documentation

10 views
Skip to first unread message

Django

unread,
Dec 10, 2013, 5:27:08 PM12/10/13
to django-...@googlegroups.com
#21591: get_messages is not covered in the documentation
--------------------------------------+--------------------
Reporter: merb | Owner: nobody
Type: Cleanup/optimization | Status: new
Component: Documentation | Version: 1.6
Severity: Normal | Keywords:
Triage Stage: Unreviewed | Has patch: 0
Easy pickings: 1 | UI/UX: 0
--------------------------------------+--------------------
Currently theres a get_messages method in the django messages framework
which could be used to get messages.
At the moment it's not covered in the documentation.

There is only one note about how to avoid clearing messages.
> [https://docs.djangoproject.com/en/dev/ref/contrib/messages/#expiration-
of-messages]

Btw. this cleanup needs to be done, since more and more people use ajax or
an REST API to query some django stuff. so you can't access the messages
in the template. It would be good if somebody will introduce the
{{{
get_messages(request)
}}}

function in the documentation.

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

Django

unread,
Dec 10, 2013, 6:31:10 PM12/10/13
to django-...@googlegroups.com
#21591: get_messages is not covered in the documentation
--------------------------------------+------------------------------------

Reporter: merb | Owner: nobody
Type: Cleanup/optimization | Status: new
Component: Documentation | Version: master
Severity: Normal | Resolution:
Keywords: messages | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0

Easy pickings: 1 | UI/UX: 0
--------------------------------------+------------------------------------
Changes (by bmispelon):

* needs_better_patch: => 0
* needs_tests: => 0
* version: 1.6 => master
* keywords: => messages
* needs_docs: => 0
* stage: Unreviewed => Accepted


Comment:

Sounds like a reasonable addition to the documentation.

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

Django

unread,
Dec 12, 2013, 5:51:40 AM12/12/13
to django-...@googlegroups.com
#21591: get_messages is not covered in the documentation
--------------------------------------+------------------------------------

Reporter: merb | Owner: nobody
Type: Cleanup/optimization | Status: new
Component: Documentation | Version: master
Severity: Normal | Resolution:
Keywords: messages | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0

Easy pickings: 1 | UI/UX: 0
--------------------------------------+------------------------------------
Changes (by Natim87):

* cc: Natim87 (added)
* has_patch: 0 => 1


Comment:

PR here : https://github.com/django/django/pull/2066

--
Ticket URL: <https://code.djangoproject.com/ticket/21591#comment:2>

Django

unread,
Dec 12, 2013, 8:57:11 AM12/12/13
to django-...@googlegroups.com
#21591: get_messages is not covered in the documentation
--------------------------------------+------------------------------------
Reporter: merb | Owner: nobody
Type: Cleanup/optimization | Status: closed
Component: Documentation | Version: master
Severity: Normal | Resolution: fixed

Keywords: messages | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0

Easy pickings: 1 | UI/UX: 0
--------------------------------------+------------------------------------
Changes (by Baptiste Mispelon <bmispelon@…>):

* status: new => closed
* resolution: => fixed


Comment:

In [changeset:"24fcca6bddca3db33ac73c29ad9167ac279e4d94"]:
{{{
#!CommitTicketReference repository=""
revision="24fcca6bddca3db33ac73c29ad9167ac279e4d94"
Fixed #21591 -- Added documentation about contrib.messages.get_messages.

Refs https://code.djangoproject.com/ticket/21591
Thanks to track user merb for the report.
}}}

--
Ticket URL: <https://code.djangoproject.com/ticket/21591#comment:3>

Reply all
Reply to author
Forward
0 new messages