You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The tokens parser is capable of catching type mismatches for scalar types but ignore the composites.
parse([{src: JSON.stringify({color: {$type: 'color',blue: {$value: '#10109A',},},dimension: {base: {$type: 'dimension',$value: '{color.blue}',// should be dimension: caught by parser ✅},},border: {base: {$type: 'border',$value: '{dimension.base}',// should be border: caught by parser ✅},nested: {$type: 'border',$value: {color: '{color.blue}',width: '{color.blue}',// should be dimension: silently failing ❌style: 'solid',},},},})}])
I think that's not much of a deal, yet I preferred to report it while looking into it.
—
The only solution I found on my end was to manually declare the mapping.
The text was updated successfully, but these errors were encountered:
nclsndr
changed the title
Nested aliases type validation
Failing nested aliases type validation
Sep 19, 2024
The tokens parser is capable of catching type mismatches for scalar types but ignore the composites.
I think that's not much of a deal, yet I preferred to report it while looking into it.
—
The only solution I found on my end was to manually declare the mapping.
The text was updated successfully, but these errors were encountered: