Try fixing packaging issues

pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "hatchling.build"
 
 [project]
 name = "dash-htmlayout"
-version = "1.0.2"
+version = "1.0.3"
 authors = [
   { name="Steve Kossouho", email="[email protected]" },
 ]
@@ -29,6 +29,12 @@ dependencies = [
 [tool.hatch.build]
 packages = ["src/dash", "src/dash/htmlayout"]
 
+[tool.hatch.build.targets.sdist]
+sources = ["src"]
+
+[tool.hatch.build.targets.wheel]
+sources = ["src"]
+
 [tool.pylint.TYPECHECK]
 ignored-modules= ["numpy", "lxml"]
 

src/DOCUMENTATION.md

@@ -43,18 +43,26 @@ Since the usual way to build a Dash layout does not involve making the whole HTM
 ```
 
 Only HTML comments and tags backed up by a component offered by the Dash libraries would be
-accepted in your document. Also, your document must have a valid root element (anything usable).
+accepted in your document. Also, your document must have a valid root element (anything usable
+that is not a `head`, `body`, `html`, `script`, etc. tag).
 
 ### Non-string parameters
 
 Any parameter for a component class can be defined as a tag attribute, as long as it is a
-`str`. Parameters that are not of type `str` can be provided in HTML using the following scheme:
+`str`. That means that string attributes can be passed as-is.
+
+```html
+<div parameter="string only">
+```
+
+Parameters that are not of type `str` can be provided in HTML using the following scheme:
 
 ```html
 <div data-parameter="python literal to evaluate" ...>
 ```
 
-For example, the `Dropdown` and `Slider` components from `dash.dcc` accept some arguments that are lists or integers, like `options` and `value`. You may pass those in HTML like follows:
+For example, the `Dropdown` and `Slider` components from `dash.dcc` accept some arguments that are lists or integers, like `options` and `value`. You may pass those in HTML like follows, prefixing the attribute with `data-` and putting a Python
+literal in the attribute string:
 
 ```html
 <dcc-slider data-value="1" data-min="0" data-max="10" data-step="5" />

src/dash/htmlayout/builder.py

@@ -3,7 +3,7 @@
 import sys
 from importlib import import_module
 from os import PathLike
-from typing import Optional, Type, Any
+from typing import Optional, Type, Any, Union
 
 from dash.development.base_component import Component
 from lxml import etree
@@ -61,7 +61,7 @@ class Builder:
     # Layout root component
     layout: Optional[Component] = None
 
-    def __new__(cls, *args, file: PathLike = None, **kwargs) -> "Builder":
+    def __new__(cls, *args, file: Union[PathLike, str] = None, **kwargs) -> "Builder":
         """
         Instanciate a new LayoutBuilder object.
 
@@ -147,7 +147,7 @@ def register_library(
             return True
         return False
 
-    def load(self, path: PathLike) -> Component:
+    def load(self, path: Union[PathLike, str]) -> Component:
         """
         Build a layout from an HTML file.
 

tests/files/simple.html

@@ -1,4 +1,4 @@
 <!-- Comments should be properly ignored -->
 <section id="content">
-    <dcc-dropdown data-options="['Red', 'Blue']"/>
+    <dcc-dropdown id="color-dropdown" data-options="['Red', 'Blue']"/>
 </section>

tests/test_builder.py

@@ -12,8 +12,12 @@ def setUpClass(cls):
         pass
 
     def test_simple_file(self):
-        simple_builder = Builder(file="files/simple.html")
-        print(simple_builder.layout)
+        """Check that components are properly built from the HTML file."""
+        builder = Builder(file="files/simple.html")
+        dropdown = builder.get_component("color-dropdown")
+        self.assertIsNotNone(dropdown)
+        self.assertIsNone(builder.get_component("invalid-dropdown"))
+        self.assertIn("Red", dropdown.options)
 
     def test_empty_file(self):
         """Check that the empty layout file creates no layout."""