Reverse-able url names. about django-ninja HOT 6 CLOSED

url_name argument added to v0.12

from django-ninja.

Hi @vitalik, I highly recommend giving the endpoint name based on the view function name. If we declare a name based on the 'url_name' parameter this is very difficult, when we have a lot of endpoints.

from django-ninja.

Hi @jlward

Yes, makes sense

from django-ninja.

I would like to reopen it. I did not find any documentation on how to use the reverse function. And in the example of the CRUD I attempted something like:

url = reverse("get_employee", kwargs={"employee_id": 1})

However, I keep getting the error Reverse for 'get_employee' not found. 'currencies' is not a valid view function or pattern name. Things like api:get_employee etc have similiar problems as namespaces seem to be unknown etc...

from django-ninja.

I wanted to add another problem in adapting the CRUD example. Suppose that you implemented the two following views described, but now with an added url_name:

@api.post("/employees", url_name="create_employee")
def create_employee(request, payload: EmployeeIn):
    employee = Employee.objects.create(**payload.dict())
    return {"id": employee.id}


@api.get("/employees", response=List[EmployeeOut], url_name="list_employees")
def list_employees(request):
    qs = Employee.objects.all()
    return qs

The reverse function does not find the create_employee anymore as it is overwritten by list_employees most likely as they have the same URL.

from django-ninja.

@fretchen
well that's the way django works
basically each url path has only one name

from django-ninja.