-
Notifications
You must be signed in to change notification settings - Fork 54
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We鈥檒l occasionally send you account related emails.
Already on GitHub? Sign in to your account
馃殌 [Feature]: htmx support #276
Comments
I use htmx (and hyperscript, alpinejs) too.
|
htmx is something that is executed in the frontend so how can we provide this as a template engine ? |
Well glad your asking here is a project that does it |
but there the html engine is used for rendering, which we already provide as template engine probably you want to have a workflow which combines the backend rendering process and active events from the frontend in one solution then you should create a request in the contrib repository for such a solution via middleware the template rendering engines are pure backend template systems which have only this one task and are independent from other feature sets |
yes i was thinking that we could add htmx as either an example or more integrated. I am totally biased. I love htmx because it allows backend devs to do frontend without going nuts. |
YES exactly !! |
If you want to have a chat about it happy to. I am in Berlin. Saw your in germany |
just join the discord channel and we can chat best you create a feature request for the contrib repository and there you(or someone) solve the combination of html template and sse/websocket in a middleware that sets up the application |
thanks @ReneWerner87 wil make a feature request and join the chat |
Here is the new issue: gofiber/contrib#679 |
Feature Description
Htmx uses go templates or any templating system to send html to the browser client in a progressive enhancement way
Additional Context (optional)
https://news.ycombinator.com/item?id=32789004 Has links bout htmx and why golang coders are using it.
Code Snippet (optional)
Checklist:
The text was updated successfully, but these errors were encountered: