Changes between Initial Version and Version 1 of Ticket #28999, comment 2


Ignore:
Timestamp:
Jan 8, 2018, 3:33:29 PM (6 years ago)
Author:
Andrew Standley

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #28999, comment 2

    initial v1  
    33Hmm, I'm not sure how to best describe my preference. It's part of a larger experimentation with the framework.
    44
    5  I'm trying to experiment with using {{{get_absolute_url}}} on my models, and I have CBV DetailView classes for my models. Firstly it seems round-about to use a URL name that represents a url->view mapping when I know the view I want. The View Class for a given Model is a core relationship that should never change, if someone uses my Models they should want to use my Views for those model. The URL name "should" not change, but it is perfectly reasonable someone may want to use my models and my views without using my urlconf. The url schema (an thus URL name) could be considered a separate matter to the models/views so I would like to de-couple these things in code for my Models/Views.
     5I'm trying to experiment with using {{{get_absolute_url}}} on my models, and I have CBV DetailView classes for my models. Firstly it seems round-about to use a URL name that represents a url->view mapping when I know the view I want. The View Class for a given Model is a core relationship that should never change, if someone uses my Models they should want to use my Views for those model. The URL name "should" not change, but it is perfectly reasonable someone may want to use my models and my views without using my urlconf. The url schema (an thus URL name) could be considered a separate matter to the models/views so I would like to de-couple these things in code for my Models/Views.
    66
    77I hope that makes sense?
Back to Top