pytest-httpchain-jsonref 0.4.0__tar.gz → 0.6.0__tar.gz

{pytest_httpchain_jsonref-0.4.0 → pytest_httpchain_jsonref-0.6.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.3
 Name: pytest-httpchain-jsonref
-Version: 0.4.0
+Version: 0.6.0
 Summary: JSON reference ($ref) support for pytest-httpchain
 Author: Alexander Eresov
 Author-email: Alexander Eresov <aeresov@gmail.com>

{pytest_httpchain_jsonref-0.4.0 → pytest_httpchain_jsonref-0.6.0}/pyproject.toml

@@ -1,6 +1,6 @@
 [project]
 name = "pytest-httpchain-jsonref"
-version = "0.4.0"
+version = "0.6.0"
 description = "JSON reference ($ref) support for pytest-httpchain"
 readme = "README.md"
 requires-python = ">=3.13"

{pytest_httpchain_jsonref-0.4.0 → pytest_httpchain_jsonref-0.6.0}/src/pytest_httpchain_jsonref/loader.py

@@ -12,6 +12,9 @@ def load_json(path: Path, max_parent_traversal_depth: int = 3, root_path: Path |
     All three directives ($include, $merge, $ref) work identically. $include and $merge are preferred
     as they avoid conflicts with VS Code's JSON Schema validation (which treats $ref specially).
 
+    "$schema" keys pass through untouched — whether and where to tolerate them
+    is the consumer's decision (pytest-httpchain's models drop them during validation).
+
     Args:
         path: Path to the JSON file to load
         max_parent_traversal_depth: Maximum number of parent directory traversals allowed in reference paths

{pytest_httpchain_jsonref-0.4.0 → pytest_httpchain_jsonref-0.6.0}/src/pytest_httpchain_jsonref/plumbing/circular.py

@@ -60,12 +60,27 @@ class CircularDependencyTracker:
         self.internal_refs.discard(pointer)
 
     def create_child_tracker(self) -> Self:
-        """Create a child tracker that inherits current state.
+        """Create a child tracker for descending into an external document.
+
+        External refs are keyed by ``(file, pointer)`` and inherited, so a
+        cross-document cycle (A -> B -> A) is detected along the resolution
+        chain.
+
+        Internal refs are NOT inherited. A JSON pointer like ``#/a`` is only
+        meaningful relative to its own document's root, and a child tracker is
+        created exactly when resolution crosses into a new document. Carrying
+        the parent's open internal pointers across that boundary would conflate
+        unrelated documents that happen to reuse the same pointer string and
+        raise a phantom cycle. Genuine intra-document internal cycles are still
+        caught, because every internal ref within one document shares a single
+        tracker instance; genuine cross-document cycles are caught by
+        ``external_refs`` (every document-crossing hop is an external ref).
 
         Returns:
-            A new tracker with copies of the current reference sets
+            A new tracker inheriting external refs but starting with a fresh,
+            empty internal-ref set.
         """
         child = self.__class__()
         child.external_refs = self.external_refs.copy()
-        child.internal_refs = self.internal_refs.copy()
+        child.internal_refs = set()
         return child