dotted-notation 0.48.0__tar.gz → 0.48.1__tar.gz

{dotted_notation-0.48.0 → dotted_notation-0.48.1}/CHANGELOG.md

@@ -3,6 +3,16 @@
 All notable changes to `dotted` are recorded here. Versions prior to
 the ones listed are omitted — browse git history for earlier entries.
 
+## [0.48.1]
+
+### Fixed
+- A sigil token in a transform argument, guard value or filter value may
+  carry a dotted path: `|min:$amount.value`, `=^lots.taken`. It is one
+  string, offered whole to a resolver with `literals = True`, and the
+  literal string without one. `$amount.value` was a `ParseError` there
+  and `^lots.taken` a raw string no resolver saw, so the transform
+  failed silently (#60). In a segment the dot still separates segments.
+
 ## [0.48.0]
 
 ### Added

{dotted_notation-0.48.0/dotted_notation.egg-info → dotted_notation-0.48.1}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: dotted_notation
-Version: 0.48.0
+Version: 0.48.1
 Summary: Dotted notation for safe nested data traversal with optional chaining, pattern matching, and transforms
 Author-email: Frey Waid <logophage1@gmail.com>
 License-Expression: MIT
@@ -1728,6 +1728,14 @@ A `$` before a word is not a substitution at all: `$str` is the plain string
     >>> dotted.get({'$amount': {'value': 2}}, '$amount.value')
     2
 
+In a guard value or transform argument the token may carry dots,
+`|min:$amount.value` or `=^lots.taken`, and is still one string; a
+[custom resolver](#custom-resolvers) reads it whole. In a segment the dot
+separates segments, so there `$amount.value` is two:
+
+    >>> dotted.get({'a': None}, 'a|coalesce:$amount.value')
+    '$amount.value'
+
 <a id="type-restrictions"></a>
 ## Type Restrictions
 

{dotted_notation-0.48.0 → dotted_notation-0.48.1}/README.md

@@ -1681,6 +1681,14 @@ A `$` before a word is not a substitution at all: `$str` is the plain string
     >>> dotted.get({'$amount': {'value': 2}}, '$amount.value')
     2
 
+In a guard value or transform argument the token may carry dots,
+`|min:$amount.value` or `=^lots.taken`, and is still one string; a
+[custom resolver](#custom-resolvers) reads it whole. In a segment the dot
+separates segments, so there `$amount.value` is two:
+
+    >>> dotted.get({'a': None}, 'a|coalesce:$amount.value')
+    '$amount.value'
+
 <a id="type-restrictions"></a>
 ## Type Restrictions
 

{dotted_notation-0.48.0 → dotted_notation-0.48.1}/dotted/grammar.py

@@ -279,6 +279,10 @@ _raw_subst = pp.Regex(r'\$[0-9]+').set_parse_action(
 # $str, a $ before a word: a plain string, as ^str is. Not $0, $(name) or $$(path).
 _dollar_word = pp.Regex(r'\$(?![0-9($])[^' + re.escape(reserved) + r' \t\n\r]+').set_parse_action(matchers.Word)
 var = _escaped_dollar | _reference | _paren_subst | _raw_subst | _dollar_word
+# In an argument or value position a sigil token may carry a dotted path,
+# |min:$amount.value or =^lots.taken: one string, for a resolver to read
+# whole. In a segment position the . separates segments, so not there.
+_arg_sigil = pp.Regex(r'(?:\$(?![0-9($])|\^)[^' + re.escape(reserved.replace('.', '')) + r' \t\n\r]+').set_parse_action(matchers.Word)
 slice = pp.Optional(integer | plus) + ':' + pp.Optional(integer | plus) \
          + pp.Optional(':') + pp.Optional(integer | plus)
 
@@ -535,7 +539,7 @@ concrete_value <<= (
 value = pp.Forward()
 _value_group_inner = value + OM(_ccomma + value)
 value_group = (S('(') + _value_group_inner + S(')')).set_parse_action(lambda t: [ct.ValueGroup(*t)])
-value <<= value_group | container_value | string_glob | bytes_literal | string | wildcard | var | regex | numeric_quoted | none | true | false | numeric_extended | numeric_slot
+value <<= value_group | container_value | string_glob | bytes_literal | string | wildcard | _arg_sigil | var | regex | numeric_quoted | none | true | false | numeric_extended | numeric_slot
 # ---------------------------------------------------------------------------
 # Concat: part+part for key construction using Python's native + operator.
 # Each part can carry per-part transforms: part|xform+part|xform
@@ -545,7 +549,7 @@ _key_atom = _commons | numeric_extended | non_integer | numeric_key | word
 _slot_atom = _commons | numeric_extended | numeric_slot
 
 # Transform: |name or |name:param — defined early so filters and guards can reference it
-targ = concrete_value | var | quoted | ppc.number | none | true | false | pp.CharsNotIn('|:')
+targ = concrete_value | _arg_sigil | var | quoted | ppc.number | none | true | false | pp.CharsNotIn('|:')
 param = (colon + targ) | colon.copy().set_parse_action(lambda: [None])
 transform = (transform_name.copy() + ZM(param)).set_parse_action(lambda s, loc, t: base.Transform(*t))
 transforms = ZM(pipe + transform)

{dotted_notation-0.48.0 → dotted_notation-0.48.1/dotted_notation.egg-info}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: dotted_notation
-Version: 0.48.0
+Version: 0.48.1
 Summary: Dotted notation for safe nested data traversal with optional chaining, pattern matching, and transforms
 Author-email: Frey Waid <logophage1@gmail.com>
 License-Expression: MIT
@@ -1728,6 +1728,14 @@ A `$` before a word is not a substitution at all: `$str` is the plain string
     >>> dotted.get({'$amount': {'value': 2}}, '$amount.value')
     2
 
+In a guard value or transform argument the token may carry dots,
+`|min:$amount.value` or `=^lots.taken`, and is still one string; a
+[custom resolver](#custom-resolvers) reads it whole. In a segment the dot
+separates segments, so there `$amount.value` is two:
+
+    >>> dotted.get({'a': None}, 'a|coalesce:$amount.value')
+    '$amount.value'
+
 <a id="type-restrictions"></a>
 ## Type Restrictions
 

{dotted_notation-0.48.0 → dotted_notation-0.48.1}/pyproject.toml

@@ -6,7 +6,7 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "dotted_notation"
-version = "0.48.0"
+version = "0.48.1"
 description = "Dotted notation for safe nested data traversal with optional chaining, pattern matching, and transforms"
 readme = "README.md"
 requires-python = ">=3.6"