htmx 0.2.1 → 0.3.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 43814b022ac875bff7a54e57794a90f77a2dbe239f34158883062aa947e0e799
-  data.tar.gz: 5d68ef44732add00a2bc32048aa668907d50fe720dc1b1b5786c3d2d3ec3b0c0
+  metadata.gz: e3bf798de3b7a08abddf9e0ebf6a46896889f08a815ea252310e43fdaf60e1b3
+  data.tar.gz: '0974300668c259fc13323bde4cf337ac9d3e87201ec07e1b0aa879346557d881'
 SHA512:
-  metadata.gz: 756f8ba0a3ffd08b05022afc74984fd633d10fe1f8e02a011e6d3468902ac58df581fea26fe2070c4ad3a23fdd7a16acadbb0f321b007e5be80bcdd68e8e000f
-  data.tar.gz: a01b465b9bbf9f89b780d69ed007e99af2f6da5ad62b4928b6dea2dff10fba8c6662913e9ac7f975990beea2735f331ee9567486b24fd5b58d370acf4ad429ec
+  metadata.gz: 91017541f831aba6aab0050a3b43c31f3020507a02f88e7aeb3f989c3884eadc1ede315abbce4f68a7be0a640594917c525683c86fafdaa1ca966b901f0299e8
+  data.tar.gz: cc38ff860e9450c0f72308be687a41c27a23ffb30ec1c0239963add89638b294a0198bc3dba8275e2058090cf1712399e5c2b6116dc4546d5f0a8a0488805725

data/README.adoc

@@ -84,7 +84,7 @@ One of the first tasks you'll want to tackle, when working with the {htmx_link}
 
 [source,ruby]
 ----
-html.button(
+tag.button(
   "Delete",
   class: "button decline",
   type: "submit",
@@ -111,7 +111,7 @@ As shown above, building HTMX attributes takes minimal effort but if you'd prefe
 ----
 prefixer = HTMX::Prefixer.new "data-hx"
 
-html.button(
+tag.button(
   "Delete",
   class: "button decline",
   type: "submit",
@@ -151,13 +151,21 @@ HTMX::Prefixer.new "bogus"
 # Invalid prefix: "bogus". Use: "hx" or "data-hx". (HTMX::Error)
 ----
 
+Some {htmx_link} attributes use dashes. For those situations, you can use strings for keys or underscored symbols to produce the correct HTMX syntax. Here's and example using both a string and symbol for keys:
+
+[source,ruby]
+----
+HTMX["swap-oob" => true, push_url: "/demo/123"]
+# {"hx-swap-oob"=>true, "hx-push-url"=>"/demo/123"}
+----
+
 === HTTP Headers
 
 When working with HTTP requests/responses, especially HTTP headers, there are a few objects that can parse and make the data easier to work with. These objects are named accordingly: request and response. Here's how to use them.
 
 ==== Request
 
-The request object allows you to obtain an immutable {data_link} object to interact with when parsing link:https://htmx.org/reference/#request_headers[HTMX HTTP request headers]. Example:
+The request object allows you to obtain a {data_link} object to interact with when parsing link:https://htmx.org/reference/#request_headers[HTMX HTTP request headers]. Example:
 
 [source,ruby]
 ----
@@ -195,7 +203,7 @@ With the above, the `.for` method plucks out only the HTMX specific headers whic
 
 ==== Response
 
-The response object allows you to obtain an immutable {data_link} object to interact with when parsing link:https://htmx.org/reference/#response_headers[HTMX HTTP response headers]. Example:
+The response object allows you to obtain a {data_link} object to interact with when parsing link:https://htmx.org/reference/#response_headers[HTMX HTTP response headers]. Example:
 
 [source,ruby]
 ----

data/htmx.gemspec

@@ -2,7 +2,7 @@
 
 Gem::Specification.new do |spec|
   spec.name = "htmx"
-  spec.version = "0.2.1"
+  spec.version = "0.3.0"
   spec.authors = ["Brooke Kuhlmann"]
   spec.email = ["brooke@alchemists.io"]
   spec.homepage = "https://alchemists.io/projects/htmx"

data/lib/htmx/headers/request.rb

@@ -3,14 +3,14 @@
 module HTMX
   module Headers
     REQUEST_KEY_MAP = {
-      "HX-Boosted" => :boosted,
-      "HX-Current-URL" => :current_url,
-      "HX-History-Restore-Request" => :history_restore_request,
-      "HX-Prompt" => :prompt,
-      "HX-Request" => :request,
-      "HX-Target" => :target,
-      "HX-Trigger-Name" => :trigger_name,
-      "HX-Trigger" => :trigger
+      "HTTP_HX_BOOSTED" => :boosted,
+      "HTTP_HX_CURRENT_URL" => :current_url,
+      "HTTP_HX_HISTORY_RESTORE_REQUEST" => :history_restore_request,
+      "HTTP_HX_PROMPT" => :prompt,
+      "HTTP_HX_REQUEST" => :request,
+      "HTTP_HX_TARGET" => :target,
+      "HTTP_HX_TRIGGER_NAME" => :trigger_name,
+      "HTTP_HX_TRIGGER" => :trigger
     }.freeze
 
     # Models the supported HTMX request headers.
@@ -28,6 +28,10 @@ module HTMX
         new(**attributes.slice(*key_map.keys).transform_keys!(key_map))
       end
 
+      def self.key_for(header, key_map: REQUEST_KEY_MAP) = key_map.fetch header
+
+      def self.header_for(key, key_map: REQUEST_KEY_MAP.invert) = key_map.fetch key
+
       def initialize boosted: nil,
                      current_url: nil,
                      history_restore_request: nil,

data/lib/htmx/headers/response.rb

@@ -32,6 +32,10 @@ module HTMX
         new(**attributes.slice(*key_map.keys).transform_keys!(key_map))
       end
 
+      def self.key_for(header, key_map: RESPONSE_KEY_MAP) = key_map.fetch header
+
+      def self.header_for(key, key_map: RESPONSE_KEY_MAP.invert) = key_map.fetch key
+
       def initialize location: nil,
                      push_url: nil,
                      redirect: nil,

data/lib/htmx/prefixer.rb

@@ -15,7 +15,7 @@ module HTMX
       validate
     end
 
-    def call(**attributes) = attributes.transform_keys! { |key| "#{default}-#{key}" }
+    def call(**attributes) = attributes.transform_keys! { |key| "#{default}-#{key}".tr "_", "-" }
 
     private
 

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: htmx
 version: !ruby/object:Gem::Version
-  version: 0.2.1
+  version: 0.3.0
 platform: ruby
 authors:
 - Brooke Kuhlmann
@@ -35,7 +35,7 @@ cert_chain:
   3n5C8/6Zh9DYTkpcwPSuIfAga6wf4nXc9m6JAw8AuMLaiWN/r/2s4zJsUHYERJEu
   gZGm4JqtuSg8pYjPeIJxS960owq+SfuC+jxqmRA54BisFCv/0VOJi7tiJVY=
   -----END CERTIFICATE-----
-date: 2023-06-19 00:00:00.000000000 Z
+date: 2023-08-11 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: refinements
@@ -108,7 +108,7 @@ required_rubygems_version: !ruby/object:Gem::Requirement
     - !ruby/object:Gem::Version
       version: '0'
 requirements: []
-rubygems_version: 3.4.14
+rubygems_version: 3.4.18
 signing_key:
 specification_version: 4
 summary: An augmenter and companion to the HTMX JavaScript library.