graphddb-runtime 0.4.3__tar.gz → 0.5.0__tar.gz

{graphddb_runtime-0.4.3 → graphddb_runtime-0.5.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: graphddb-runtime
-Version: 0.4.3
+Version: 0.5.0
 Summary: Thin DynamoDB executor for GraphDDB-generated Python repositories (single-operation core, issue #44).
 License: MIT
 Requires-Python: >=3.9

{graphddb_runtime-0.4.3 → graphddb_runtime-0.5.0}/graphddb_runtime.egg-info/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: graphddb-runtime
-Version: 0.4.3
+Version: 0.5.0
 Summary: Thin DynamoDB executor for GraphDDB-generated Python repositories (single-operation core, issue #44).
 License: MIT
 Requires-Python: >=3.9

{graphddb_runtime-0.4.3 → graphddb_runtime-0.5.0}/graphddb_runtime.egg-info/SOURCES.txt

@@ -38,4 +38,5 @@ tests/test_integration_unique.py
 tests/test_maintain.py
 tests/test_middleware.py
 tests/test_relations.py
+tests/test_ttl.py
 tests/test_unit.py

{graphddb_runtime-0.4.3 → graphddb_runtime-0.5.0}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "graphddb-runtime"
-version = "0.4.3"
+version = "0.5.0"
 description = "Thin DynamoDB executor for GraphDDB-generated Python repositories (single-operation core, issue #44)."
 readme = "README.md"
 requires-python = ">=3.9"

graphddb_runtime-0.5.0/tests/test_ttl.py

@@ -0,0 +1,57 @@
+"""Issue #172 (Epic #167 — CFn generator C4): DynamoDB TTL.
+
+The `@ttl` field decorator marks a model's Time-To-Live attribute. Because TTL is a
+**physical schema** fact (unlike the maintenance/stream signals kept off the
+manifest) and the CloudFormation emitter consumes the manifest, the TTL attribute
+name flows into `manifest.json` as `entities.<Model>.ttlAttribute`.
+
+This module locks the **Python-visible** manifest value: the Python bridge reads the
+SAME `manifest.json` the TS generator emitted, so this asserts the TTL fact reaches
+Python identically (TS↔Python parity — a single producer, so byte-identical by
+construction). A model without `@ttl` carries no `ttlAttribute` key (backward
+compatible). The corresponding TS-side assertions live in
+`__tests__/spec/ttl-manifest.test.ts` and `__tests__/codegen/cloudformation.snapshot.test.ts`.
+"""
+
+from __future__ import annotations
+
+import json
+
+import conftest
+
+
+def _manifest() -> dict:
+    with open(conftest.MANIFEST_PATH, encoding="utf-8") as fh:
+        return json.load(fh)
+
+
+def test_manifest_carries_ttl_attribute_for_ttl_model() -> None:
+    session = _manifest()["entities"]["SessionModel"]
+    # The `@ttl expiresAt!: number` field is the table's TTL attribute.
+    assert session["ttlAttribute"] == "expiresAt"
+    # It is a NON-key attribute, stored as a Number (epoch seconds).
+    assert session["fields"]["expiresAt"]["type"] == "number"
+
+
+def test_non_ttl_model_has_no_ttl_attribute_key() -> None:
+    # A model with no `@ttl` field carries no `ttlAttribute` key (byte-identical to
+    # the pre-#172 manifest — backward compatible).
+    user = _manifest()["entities"]["UserModel"]
+    assert "ttlAttribute" not in user
+
+
+def test_at_most_one_ttl_attribute_per_physical_table() -> None:
+    # DynamoDB allows exactly one TTL attribute per table; the generator enforces
+    # this at manifest build. Confirm the whole manifest never lands two distinct
+    # TTL attributes on one physical table.
+    manifest = _manifest()
+    by_table: dict[str, set[str]] = {}
+    for entity in manifest["entities"].values():
+        attr = entity.get("ttlAttribute")
+        if attr is None:
+            continue
+        by_table.setdefault(entity["physicalName"], set()).add(attr)
+    for physical, attrs in by_table.items():
+        assert len(attrs) == 1, (
+            f"physical table {physical!r} has multiple TTL attributes: {attrs}"
+        )