If you think it's a good deal, You could've bought one in Detroit for $1
Michal
yeah it should definitely be part a of the url. It will be if you define a parametrized url. More details in the documentation https://docs.djangoproject.com/en/5.1/topics/http/urls/#url-dispatcher
In django you will typically define the url pattern with uuid
being a keyword path parameter, and in the view code you can use get_object_or_404(Model, uuid=kwargs['uuid'])
. This way the user will see a standard 404 page if they attempt to view a page with uuid that does not exist.
Of course, if you use class based views, you can extend detail view based off uuid, and the base class with handle the 404 page for you, so there'll be no need for get_object_or_404
.
I am assuming you will want to use class based views for this so you can extract the common functionality into a base class or a mixin and reuse it in a number of views.
EDIT: I may have misunderstood the question wrong originaly. It looks like you want to bypass authentication for a subset of urls (or views). Authentication is not required by default in django, you can add LoginRequiredMixin
(or a decorator) to your view, so not including the mixin would be a way to bypass the login requirement. Do you want to share relevant parts of your code for better suited advice?
Someone made a mural in Brazil but it was removed for safety.
https://www.jalopnik.com/real-life-wile-e-coyote-drives-fiat-smack-into-paintin-1765745078/
Operation crayon