Add use-case example

digitallyinduced · Nov 1, 2024 · baafd7c · baafd7c
1 parent 502aa2d
commit baafd7c
Show file tree

Hide file tree

Showing 2 changed files with 2 additions and 0 deletions.
diff --git a/Guide/hsx.markdown b/Guide/hsx.markdown
@@ -362,6 +362,7 @@ The custom HSX will validate that tags and attributes are either in the default
 This approach is particularly useful for:
 - Web Components with custom attribute names
 - UI libraries with non-standard attributes
+- Domain-specific XML markup languages like [Hyperview](https://hyperview.org/docs/example_navigation)
 - Integration with third-party frameworks that extend HTML syntax
 
 It's not usable for libraries with highly esoteric attributes, like Alpine.js.  Even `uncheckedHsx` will throw an error because it doesn't recognize html attributes starting with `@` or has `:` in the attribute name. In these cases, the spread syntax `{...attributeList}` is likely your best bet.

diff --git a/ihp-hsx/README.md b/ihp-hsx/README.md
@@ -358,6 +358,7 @@ The custom HSX will validate that tags and attributes are either in the default
 This approach is particularly useful for:
 - Web Components with custom attribute names
 - UI libraries with non-standard attributes
+- Domain-specific XML markup languages
 - Integration with third-party frameworks that extend HTML syntax
 
 It's not usable for libraries with highly esoteric attributes, like Alpine.js.  Even `uncheckedHsx` will throw an error because it doesn't recognize html attributes starting with `@` or has `:` in the attribute name. In these cases, the spread syntax `{...attributeList}` is likely your best bet.