X'inhuma views f'Django?

Question

Accepted Answer

**view** hija l-livell tal-logika ta' Django — funzjoni jew klassi li tirċievi HTTP **request**, teżekuta l-logika (interrogazzjoni tal-mudelli, ipproċessar tal-input), u tirretorna HTTP **response**. Views huma fejn inti timmaniġġaw x'jiġri meta URL jiġi aċċessat.

## Function-based views (FBVs)

```python
from django.shortcuts import render, get_object_or_404
from django.http import JsonResponse, HttpResponse

def article_list(request):
    articles = Article.objects.all()                    # query models
    return render(request, "articles.html", {"articles": articles})  # render a template

def article_detail(request, pk):
    article = get_object_or_404(Article, pk=pk)         # 404 if not found
    return render(request, "detail.html", {"article": article})

def api_articles(request):
    data = list(Article.objects.values("title", "body"))
    return JsonResponse(data, safe=False)               # return JSON instead of HTML
```

Function-based view tirċievi `request` (flimkien ma' kwalunkwe parametri URL), tagħmel ix-xogħol tagħha, u terġa' tarretorna response — `render()` għal HTML, `JsonResponse` għal JSON, `HttpResponse` għal output ta' biss.

## Immaniġġar metodi HTTP u input differenti

```python
def create_article(request):
    if request.method == "POST":
        form = ArticleForm(request.POST)
        if form.is_valid():
            form.save()
            return redirect("article_list")             # redirect after a successful POST
    else:
        form = ArticleForm()
    return render(request, "create.html", {"form": form})
```

Views jispezzjonaw `request.method` (GET, POST, eċċ.) u jaċċessaw l-input permezz ta' `request.POST`, `request.GET`, `request.user`, eċċ.

## Class-based views (CBVs) — riutilizzabbli, inqas boilerplate

```python
from django.views.generic import ListView, DetailView

# generic CBVs handle common patterns with minimal code
class ArticleListView(ListView):
    model = Article                                     # automatically lists all articles
    template_name = "articles.html"

class ArticleDetailView(DetailView):
    model = Article
```

Django joffri wkoll **class-based views** — inklużi generic views (`ListView`, `DetailView`, `CreateView`) li jimplimentaw mudelli komuni (listing, detail, CRUD) b'kod żgħir ħafna, riduċendu l-boilerplate.

## Ir-rwol tal-view fil-fluss tar-request

```text
Request → URL routing → VIEW (logic) → queries models, renders template → Response
The view is the orchestrator: it connects the URL, the data (models), and the
presentation (template) to produce a response.
```

## Għaliex Importanti

Views huma l-livell tal-logika ta' Django (il-"V" f'MVT, ekwivalenti għat-controller ta' MVC) — fejn inti timmaniġġaw kull request, jagħmluhom fundamentali għal bini ta' kwalunkwe applikazzjoni Django.

Fhim views huwa essenzjali għaliex huma l-orchestrators li jgħaqdu kollox flimkien: jirċievu r-request, japplikaw il-logika tal-negozju, jinterroġaw mudelli għad-data, jipproċessaw input tal-utent (formoli), u jirretornaw ir-response xieraq (HTML permezz ta' templates, jew JSON għal APIs).

Igħarraf kif tikteb **function-based views** (espliċiti, flessibli — tajbin għal logika custom), immaniġġar metodi HTTP differenti u aċċess ta' data tal-request, u uża **class-based/generic views** (li jirriduku b'mod drammatiku l-boilerplate għal mudelli komuni bħal listing u CRUD) jkoprija l-ispettru prattiku tal-bini ta' Django endpoints.

Views huma fejn jgħixu l-aktar loġika tal-immaniġġment tal-request tal-applikazzjoni, għalhekk mastering tagħhom — iċ-ċiklu tar-request/response, l-għażla bejn approaches function-based u class-based, u kif views jkonnettjaw URLs ma' mudelli u templates — hija għarfien fundamental, ta' kuljum għal kwalunkwe developer ta' Django u ċentrali għalkemm il-framework jipproċessa r-requests.