https://htmx.org logo
Powered by
# htmx-general
  • m
    and the data leads to a detail
  • m
    is pretty common
  • m
    (added a push url)
  • m
    alternatively, if you are using hx-boost, you don't need to do anything else and can just make those normal links
  • m
  • m
    basically you just write a normal web app, but return html fragments if the request is from htmx (there is a header you can check). Or, if that's too much of a pain, you can use the hx-select attribute to select out the html fragment you want. 🙂
  • b
    hm... it is not trivial for me to tell the API to return html i am afraid ( ia m using django restframework)
  • b
    i did it before with django-htmx but this is not done via api thix way
  • b
    i already have the api up and running and the lovely django-htmx package from adamchainz is unfortunately is directly connecting to djangos views and not to an api
  • m
    Right, so you could use the client-side-templates plugin if you want to transform JSON into a table OR you could add another end point for the table that returns HTML. I'd lean towards the latter, but it's up to you.
  • b
    i am trying to figure out on how to differentiate if the incoming request id from htmx or something else which would still need to respond in json
  • m
  • m
    HT-Request
    will be true
  • m
    I believe there is a property available via the django plugin for this, one sec
  • m
  • m
    Copy code
    python
def my_view(request):
    if request.htmx:
        template_name = "partial.html"
    else:
        template_name = "complete.html"
    return render(template_name, ...)
  • m
    looks like it could be modified for your needs
  • b
    this is what i am doing now, but this uses django views and not the api
  • m
    hmm, I don't know what "the api" means. Any django users able to jump in here?
  • b
    atm i am thinking of how to let the django restframework decide on how to answer with html and how that can be done (probably possible)
  • u
    @User just change the reponse object. Instead of using the DRF Response with the serializer data, just return a normal render with a template (use the header to make the decision). Should work, I guess.
  • b
    you mean for example in the def list() of the viewset?
  • u
    Copy code
    def my_view(request):
    if request.htmx:
        return render(request, "partial.html", context)
    else:
        return Response(serializer.data, status=...)
  • b
    but this is again not with the api but the normal view
  • b
    basically like adamchainz code suggests iz
  • u
    There's no difference between a 'API View' or a 'normal View'
  • u
    What View's return is what makes it a REST response or a template render.
  • b
    one time DRF hands the data to the endpoint, one time vanilla django does the job?
  • u
    To achieve what you are trying to do, yes.
  • b
    but I want to use DRF for my json respones and HTMX. wouldn't that be smarter (same logic, just response is mantled in JSON or html style)
1...270271272...1146Latest