Probably you need something like this

thanks dude

not really used to neither quarkus or htmx

having to do a project for my internship with both

living my best life

Your fields in form should be annotated as form params like this

@FormParam("username") private String username;

@orange-air-11609 here you have entire todo app using htmx and quarkus

this how my class is built

yeah already seen it

thanks

It is an entity. It's related to database. This class should not be used to data transfer from html forms. You should have separate classes

I'm trying to debug a situation and not sure where to start. I have a landing page (

/home/

) with

hx-boost

enabled and there's a link to

/services/#speeches

. Clicking on the link does the following: 1) briefly puts

/services/#speeches

in the URL bar and loads the page (not sure which happens first) 2) scrolls to

#speeches

3) changes the url in the navigation bar to just

/services/

Then, if I click "back" in the browser, it 1) Scrolls up the Services page (to about the location of the initial link clicked on the home page) 2) puts

/home/#speeches

in the URL bar (although the page it's showing is part of the Services page) Any suggestions on what I should look for?

Looks like a bug. Create issue on github

sad that this article doesn't mention htmx https://github.com/readme/featured/server-side-languages-for-front-end

Maybe this would help: https://htmx.org/attributes/hx-push-url/

Thought it might be, but figured it might just be my implementation. Trying to find a link with an anchor on the official htmx site to see if I can recreate it there

Hmm, I wonder if manually specifying the push-url with the anchor would fix it

Yeah it might. I've never used it with anchors in the URL but I don't see why it wouldn't work.

Issue seems to be around here: https://github.com/bigskysoftware/htmx/blob/master/dist/htmx.js#L2577 It seems like the link is setting the hash on the initial page? The URL bar is starting at

/home/

then getting

/home/#speeches

then finally

/services/#speeches

. I'll file a bug on GH, but wasn't able to find temporary workaround

😑 history is an endless source of bugs. Will have time next week to fix it.

Sorry to be a downer 🙂 Thanks for your work on this!

eternal pain

the history api

eternal pain

question for the group: One problem (and there is only one, yeah right, mmhmmm) with history is what was run into a few days ago, where forms that are snapshotted to the history cache don't have their values saved. I see two different options to solve this (aside from disabling the history cache if it matters to you): 1) When we take the snapshot, we can move the current value of the input into the HTML we save. So, for example, a text-input would have it's value attribute set to it's value property. This is moderately complex and a little annoying, but doable. 2) Allow people to add an attribute to a page, say

hx-do-not-cache

that will signal to htmx not to cache that particular page. This is simple, but requires more user intervention obviously. What do people think?