Why should only a-tag and form-tag* be able to make HTTP requests?
Why should only click & submit events trigger them?
Why should only GET & POST methods be available?
Why should you only be able to replace the entire screen?
If this is what you need, and you have a decent backend, then doing it with htmx is far more comfortable as almost all your logic is now back where it belongs (and where you have access to sane languages): The backend.
-- a backend dev who also has to do frontend
* I can’t wait for Lemmy markdown to stop being fucking broken …
So you get angled-bracket-opening letter-a angled-bracket-closing (or in other words, an HTML a-Tag), but not formatted as code? That is weird as fuck.
const foo=""
That is meaningless, Lemmy doesn’t have issues with code, only with certain symbols.
If this is what you need, and you have a decent backend, then doing it with htmx is far more comfortable as almost all your logic is now back where it belongs (and where you have access to sane languages): The backend.
-- a backend dev who also has to do frontend
* I can’t wait for Lemmy markdown to stop being fucking broken …
LOL most of your markdown rendered fine in Voyager.
I can see some benefits, unfortunately they’re not issues I deal with in our current stack.
Does this render fine? `` (angled-bracket-opening letter-a angled-bracket-closing, formatted as code), because I didn’t post non-working stuff.
Looks fine, but I didn’t get highlighting
It didn’t show on webpage są code, but works in Jerboa app. If you want to render block of code use three `
So you get angled-bracket-opening letter-a angled-bracket-closing (or in other words, an HTML a-Tag), but not formatted as code? That is weird as fuck.
That is meaningless, Lemmy doesn’t have issues with code, only with certain symbols.
It’s just two backticks with nothing between, so probably not.
That is what should be there thanks to Lemmy’s markdown issues, and why what the other person said was deeply confusing for me.