Version 0.5.0

Changelog

• Feat: Add the RenderHTML method to htmx.Response to render template.HTML values.
• Feat: Add MustWrite MustRenderHTML and MustRenderTempl methods to htmx.Response.
  • Inspired by v1.6.0 of donseba/go-htmx adding must/just helpers.

Full Changelog: v0.4.1...v0.5.0

Version 0.4.1

Changelog

• @julianooi Fix: Using Response.LocationContext should no longer always result in an error while writing a response. (Commit: 9703a2d, PR: #5)

Full Changelog: v0.4.0...v0.4.1

Version 0.4.0

Thanks for the appreciation for my library. Your enthusiasm for HTMX is amazing!

Changelog

• f8167a3 New feature: Add the Swap Strategy API. SwapStrategy values for HX-Reswap can now have modifiers added to them in a type-safe way. (#1)
  • 8e2d8f8 @rafiramadhana Test: Added tests for Swap Strategy methods. (#4)
• c6ac95c Fix: LocationContext should now render SwapStrategy values without errors.
• d8939a5 Docs: Doc comment links to other parts of htmx-go have been added.

Full Changelog: v0.3.0...v0.4.0

3️⃣ Version 0.3.0

Because having just one release in a day isn't enough. 😅

Changelog

• New HTTP status code: htmx.StatusStopPolling is a constant with the value 286 that tells HTMX to stop polling for an element.
• Bug fix: The type of the Values field in htmx.LocationContext has been modified from []string to map[string]string.
  • I saw that the type in the equivalent HTMX Django library (reference) is a dict[str, str], so here it should be the equivalent, map[string]string.
• Documentation: Added a few more links to the HTMX documentation in the exported doc comments.
  • Happy document reading!

Version 0.2.0

Changelog

• New feature: TriggerObject (formerly TriggerKeyValue) can now accept any value. Be sure to only feed it JSON-serializable objects! Maybe use map[string]string to be safe.
• BREAKING CHANGE: rename TriggerValue into TriggerDetail
• BREAKING CHANGE: rename TriggerKeyValue into TriggerObject

Full Changelog: v0.1.0...v0.2.0