Ensure reference design tokens don't include .value

[adamstankiewicz]

Currently, all the reference design tokens include .value in their value strings, e.g.:

paragon/tokens/src/global/color.json

Lines 29 to 60 in 9fb7e98

	"value": "{color.primary.base.value}",
	"source": "$primary-100",
	"modify": [
	{
	"type": "mix",
	"otherColor": "white",
	"amount": "0.94"
	}
	]
	},
	"200": {
	"value": "{color.primary.base.value}",
	"source": "$primary-200",
	"modify": [
	{
	"type": "mix",
	"otherColor": "white",
	"amount": "0.75"
	}
	]
	},
	"300": {
	"value": "{color.primary.base.value}",
	"source": "$primary-300",
	"modify": [
	{
	"type": "mix",
	"otherColor": "white",
	"amount": "0.50"
	}
	]
	},

However, the .value is implied in the reference token string value. That is, {color.primary.base} should be equivalent to {color.primary.base.value}.

• Is there an explicit need in our implementation where .value needs to be included in the reference token value strings?
• If so (presumably due to custom formatters/transforms), can those be refactored slightly to infer the .value as needed?

Further explanation, pretty much all the docs / examples about style-dictionary tend to not include .value in the reference token value strings.

[PKulkoRaccoonGang]

PRs:
Paragon - #1989
Brand - edx/brand-edx.org#45

[adamstankiewicz]

Closing this issue as the PR is up for @edx/brand but we don't have an alpha release tag for @edx/brand to merge it yet. Also opened #2026 to track this work.