@daikin-oss/dds-tokens 0.3.0 → 0.3.1

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/CHANGELOG.md CHANGED
@@ -1,5 +1,11 @@
1
1
  # Changelog
2
2
 
3
+ ## 0.3.1
4
+
5
+ ### Patch Changes
6
+
7
+ - [#43](https://github.com/dsv-rp/dds-tokens/pull/43) [`f337cef`](https://github.com/dsv-rp/dds-tokens/commit/f337ceffd68b769f50bba793d3ce010a50b09ab9) Thanks [@yodas7](https://github.com/yodas7)! - Add Tokens Studio type to the tokens in the JSON outputs.
8
+
3
9
  ## 0.3.0
4
10
 
5
11
  ### Minor Changes
package/README.md CHANGED
@@ -97,6 +97,6 @@ Import individual themes:
97
97
 
98
98
  There are JSON files under `json/` that lists the types and values of the tokens.
99
99
  These are basically for internal use and are used to integrate design tokens with Tailwind CSS.
100
- The structure of the JSON files is `{ "<token name>": ["<token value>", "<token type>"] }`.
100
+ The structure of the JSON files is `{ "<token name>": ["<token value>", "<style-dictionary token type>", "<tokens-studio token type>" | null] }`.
101
101
 
102
102
  In addition, the theme JSON files before building, which are located in `themes/`, are also published in the same path in the package.