You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The biggest advantage of separating frontend and backend is being able to define declarative components on the frontend. This allows a certain degree of certainty about how the ui would be presented.
Would providing support for html templates and slots be a non-goal for the htmx? if not, it’ll be great designate a template as a target and use api json response to populate it’s slots.
It’ll also allow htmx to co-exist on api driven frontends and other frameworks.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
The biggest advantage of separating frontend and backend is being able to define declarative components on the frontend. This allows a certain degree of certainty about how the ui would be presented.
Would providing support for html templates and slots be a non-goal for the htmx? if not, it’ll be great designate a template as a target and use api json response to populate it’s slots.
It’ll also allow htmx to co-exist on api driven frontends and other frameworks.
Beta Was this translation helpful? Give feedback.
All reactions