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
when the client lets the server autocomplete one of the hx-ext="{extension}" and the header is specified in the current tree, add the script source to it.
ex. Add <script src="https://unpkg.com/htmx.org/dist/ext/event-header.js"></script>
to the header when the extension is completed using the lsp:
<buttonhx-ext="event-header">
Click Me!
</button>
The text was updated successfully, but these errors were encountered:
I like the idea of supporting quasi "auto imports" but don't think that adding a script tag to the head is the answer. Now my personal usage of htmx is purely script tags in <head>, but htmx also supports npm-like imports and I'm sure there are other people who want to lazy load extensions. This behaviour would probably annoy a certain subset of users.
We could support an "informational" code action on the extension usage if we don't see the extension imported in the head, but I also think that would raise a bunch of false positives (once again when other loading strategies are used). I like the idea, but am not sure how to eliminate annoyance.
when the client lets the server autocomplete one of the hx-ext="{extension}" and the header is specified in the current tree, add the script source to it.
ex. Add
<script src="https://unpkg.com/htmx.org/dist/ext/event-header.js"></script>
to the header when the extension is completed using the lsp:
The text was updated successfully, but these errors were encountered: