Version 0.8 brings basic Datastar support 🚀

[stroiman]

Version 0.8 is the culmination of the attempt to support Datastar, for which quite a lot of functionality had to be reworked.

• Datastar uses streaming data from fetch responses, dictating changes to the event loop, and finding ways to write tests with predictable execution patters.
• Adding support for fetch in general
• AbortController and AbortSignal support
• Datastar is distributed as ES modules, requiring adding support in v8go (the changes will hopefully make their way to https://github.com/tommie/v8go eventually)
• The use of Element.dataset required implementing named handlers in v8go (should also eventually make it's way to tommie's fork).
• Implementing MutationObserver
• And many other smaller changes where operations or attributes were not implemented (including improved error messages, so you know that a test fails because of calling into an unsupported API)

In the process, many more elegant and idiomatic solutions were discovered (and a few bugs). Go's context package is used extensively to control abortion, and internally, AbortSignals communicate abort through context cancellation.

Only the most basic use case works so far

The only working feature so far is an element with a data-on-click="@get('/datastarapi/events')", where the response is morphed into the DOM. There's only just enough to get this scenario working. E.g., only GET requests are supported so far.

In fact, the only option that fetch supports currently is the signal. No headers, no body.

The ability to simulate user interaction is also very limited so far, only a basic Click() function is implemented. You can manually dispatch events from elements, e.g. KeyDown. It's a planned feature to simulate the user typing some input, automatically dispatching keydown/keyup/keypress/input events in the correct order from an input string.

Priority

The priority going forward is further improving fetch, but user feedback can affect priorities.

[joeblew999]

Very cool !!

is there an example Datastar project to try it on ?

[stroiman]

Not a "real" project, just a very basic example in this project's own test suite - which also reflect what currently works.

The HTML is here: https://github.com/gost-dom/browser/blob/main/internal/test/integration/test-app/content/ds/index.html
The controller, responding with a merge-fragments: https://github.com/gost-dom/browser/blob/main/internal/test/integration/test-app/datastar.go

And the test that verifies the behaviour of fragment merging:
https://github.com/gost-dom/browser/blob/main/scripting/v8host/datastar_test.go

The test is currently packed with code comments, primarily as I don't have other documentation yet.

I hope you'll try it out, have the patience for the rough edges, and share your experiences, so I can get feedback about what works well, and what doesn't, as well as

[stroiman]

The HTML file also has an input bound to a signal; but that doesn't work in the current release. But I have just enough for that to work in a feature branch, so expect that coming soon :)