unitysvc-data 0.2.10__tar.gz → 0.2.11__tar.gz

{unitysvc_data-0.2.10/src/unitysvc_data.egg-info → unitysvc_data-0.2.11}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: unitysvc-data
-Version: 0.2.10
+Version: 0.2.11
 Summary: Standard examples and presets for UnitySVC data packages
 Author-email: Bo Peng <bo.peng@unitysvc.com>
 Maintainer-email: Bo Peng <bo.peng@unitysvc.com>

{unitysvc_data-0.2.10 → unitysvc_data-0.2.11}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "unitysvc-data"
-version = "0.2.10"
+version = "0.2.11"
 description = "Standard examples and presets for UnitySVC data packages"
 readme = "README.md"
 authors = [{ name = "Bo Peng", email = "bo.peng@unitysvc.com" }]

{unitysvc_data-0.2.10 → unitysvc_data-0.2.11}/src/unitysvc_data/presets.py

@@ -135,13 +135,33 @@ _PRESET_PARAMETERS: dict[str, dict[str, str]] = {}
 _PRESET_APPLIES_TO: dict[str, dict[str, Any]] = {}
 
 for _name, _entry in MANIFEST["presets"].items():
+    # ``applies_to`` rides along inside ``meta`` so it survives into the
+    # document record. It is a SELECTION predicate -- which services get this
+    # example -- and it used to be dropped here, leaving the title as the only
+    # trace of it. A consumer then had to read the axes back out of prose:
+    # "Python code example (vision, requests)" is capability, feature and
+    # client flattened into one string, and `Anthropic-style (streaming)`
+    # collapses two axes into one label, so it cannot be split apart reliably.
+    #
+    # Shipped as the dict, not a flattened list of "Capability :: Chat"
+    # strings: a consumer grouping by axis wants keyed access, and a flat list
+    # would have to be split back apart to recover which axis each entry
+    # belongs to. See unitysvc/unitysvc-data#95 and the consumer design note
+    # at unitysvc/unitysvc docs/dev-notes/frontend/code-example-classifiers.md.
+    #
+    # Omitted entirely when empty, so a universal document (``llm_description``
+    # constrains nothing) keeps today's shape instead of gaining an empty dict.
+    _applies = dict(_entry.get("applies_to", {}))
+    _meta = dict(_entry.get("meta", {}))
+    if _applies:
+        _meta["applies_to"] = _applies
     _PRESET_RECORDS[_name] = {
         "category": _entry["category"],
         "description": _entry["description"],
         "file_path": _resolve_example_path(_entry["example_file"]),
         "is_active": _entry["is_active"],
         "is_public": _entry["is_public"],
-        "meta": dict(_entry.get("meta", {})),
+        "meta": _meta,
         "mime_type": _entry["mime_type"],
     }
     # ``parameters`` was added in manifest schema v1.1 — older
@@ -176,7 +196,13 @@ def _make_factory(record: dict[str, Any]):
         out = deepcopy(record)
         for key, value in overrides.items():
             if key == "meta" and isinstance(value, dict) and isinstance(out.get("meta"), dict):
-                out["meta"] = {**out["meta"], **value}
+                # ``applies_to`` is platform-owned. A seller may add and
+                # override any other meta key, but not this one: the registry
+                # validates the preset's values at build time, and an override
+                # would hand a consumer an unregistered value with nothing
+                # having checked it.
+                seller = {k: v for k, v in value.items() if k != "applies_to"}
+                out["meta"] = {**out["meta"], **seller}
             else:
                 out[key] = value
         return out

{unitysvc_data-0.2.10 → unitysvc_data-0.2.11/src/unitysvc_data.egg-info}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: unitysvc-data
-Version: 0.2.10
+Version: 0.2.11
 Summary: Standard examples and presets for UnitySVC data packages
 Author-email: Bo Peng <bo.peng@unitysvc.com>
 Maintainer-email: Bo Peng <bo.peng@unitysvc.com>

{unitysvc_data-0.2.10 → unitysvc_data-0.2.11}/tests/test_presets.py

@@ -851,3 +851,71 @@ def test_parse_source_accepts_unknown_keys_message_lists_params():
     """Sentinel parsing errors should mention $params is a valid key."""
     with pytest.raises(ValueError, match=r"'\$params'"):
         doc_preset({"$preset": "s3_connectivity_v1", "$nope": {}})
+
+
+# ---------------------------------------------------------------------------
+# applies_to rides along in meta (unitysvc-data#95)
+# ---------------------------------------------------------------------------
+def test_a_document_carries_its_applies_to_in_meta():
+    """The selection predicate survives into the document record.
+
+    It used to be dropped, leaving the title as its only trace -- so a consumer
+    wanting to group examples by capability had to read the axes back out of
+    prose like "Python code example (vision, requests)", where
+    `Anthropic-style (streaming)` collapses two axes into one label and cannot
+    be split apart reliably.
+    """
+    record = doc_preset("llm_code_example_vision_requests")
+
+    assert record["meta"]["applies_to"] == {
+        "capability": "image-text-to-text",
+        "dialect": "openai",
+        "feature": "vision",
+        "upstream": "openai",
+    }
+
+
+def test_it_is_a_dict_not_a_flattened_list():
+    """Consumers group by axis, which wants keyed access.
+
+    A flat ``["Capability :: Vision", …]`` would have to be split back apart to
+    recover which axis each entry belongs to -- rebuilding the dict it threw
+    away. The flat shape suits discovery; this is selection.
+    """
+    applies_to = doc_preset("llm_code_example_vision_requests")["meta"]["applies_to"]
+
+    assert isinstance(applies_to, dict)
+    assert set(applies_to) <= {"capability", "dialect", "upstream", "feature"}
+
+
+def test_the_other_meta_keys_are_untouched():
+    meta = doc_preset("llm_code_example_vision_requests")["meta"]
+
+    assert meta["variant"] == "Vision"
+    assert meta["requirements"] == ["requests"]
+
+
+def test_a_document_that_constrains_nothing_gains_no_empty_dict():
+    """``llm_description`` applies to every service, so it has no predicate.
+
+    An empty ``applies_to`` is omitted rather than shipped as ``{}``, keeping
+    today's payload shape -- the same stance the backend's customer projection
+    takes when nothing survives its allowlist.
+    """
+    meta = doc_preset("llm_description").get("meta") or {}
+
+    assert "applies_to" not in meta
+
+
+def test_a_seller_cannot_override_applies_to():
+    """Platform-owned: the registry validates the PRESET's values at build
+    time, so an override would hand a consumer an unregistered value with
+    nothing having checked it. Every other meta key stays seller-overridable.
+    """
+    record = doc_preset(
+        "llm_code_example_vision_requests",
+        meta={"applies_to": {"capability": "not-a-capability"}, "note": "mine"},
+    )
+
+    assert record["meta"]["applies_to"]["capability"] == "image-text-to-text"
+    assert record["meta"]["note"] == "mine"