Opened 10 years ago

Last modified 6 weeks ago

#24162 assigned New feature

"Method Flowchart" for all CB(G)V documentation pages — at Initial Version

Reported by: Ivan Ven Osdel Owned by: nobody
Component: Documentation Version: 1.7
Severity: Normal Keywords: CBV CBGV method flowchart
Cc: tomas.ehrlich@…, Clifford Gama Triage Stage: Accepted
Has patch: no Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: no UI/UX: no
Pull Requests:How to create a pull request

Description

First off, to whoever had the idea and put in the effort to add the "Method Flowchart" to the CBV and CBGV doc pages, thank you, thank you, thank you. So helpful.

So naturally I would love to see the feature on all of the CB(G)V pages, particularly those with a form as they are more complicated.

Why is this necessary?

  1. To make the multiple branches of form view logic more explicit. What methods get called when there is a GET? What about a POST?
  1. To gain all the advantages that the "Method Flow" chart has provided to the other views. For me it has been primarily helpful for understanding and figuring out how to avoid duplicate queries.

Moved from comment on: ticket:20608

According to the ticket's flags, the next step(s) to move this issue forward are:

  • To provide a patch by sending a pull request. Claim the ticket when you start working so that someone else doesn't duplicate effort. Before sending a pull request, review your work against the patch review checklist. Check the "Has patch" flag on the ticket after sending a pull request and include a link to the pull request in the ticket comment when making that update. The usual format is: [https://github.com/django/django/pull/#### PR].

Change History (0)

Note: See TracTickets for help on using tickets.
Back to Top