Skip to content

Commit e280eee

Browse files
committed
Overhaul of scope resolution - Fixes MadLittleMods#2 - v0.3.1
1 parent f38f059 commit e280eee

13 files changed

+775
-494
lines changed

CHANGELOG.md

Lines changed: 8 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,21 +1,25 @@
11

2+
# v0.3.1 - 2015-5-5
23

3-
# 0.2.3 - 2015-5-4
4+
- Large overhaul of code to make it more robust on proper scope resolution.
5+
- Fix #2
6+
7+
# v0.2.3 - 2015-5-4
48

59
- Add support for CSS4 descendant selector `>>` syntax
610

711

8-
# 0.2.2 - 2015-5-1
12+
# v0.2.2 - 2015-5-1
913

1014
- Automatically prefix any variables defined in `options.variables` with `--` (according to CSS custom property syntax).
1115

12-
# 0.2.1 - 2015-4-30
16+
# v0.2.1 - 2015-4-30
1317

1418
- Added support for descendant selector nesting instead of just physical space nesting
1519
- Fixed issue with comma separated rules. It was throwing a undefined is not a function error
1620
- Moved to external scope check `isUnderScope` instead of integrated into `resolveValue`
1721
- Added test for empty `var()` call. See [test/fixtures/empty-var-func.css](https://github.com/MadLittleMods/postcss-css-variables/blob/master/test/fixtures/empty-var-func.css)
1822

19-
# 0.1.0 - 2015-4-29
23+
# v0.1.0 - 2015-4-29
2024

2125
- First release

README.md

Lines changed: 4 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@ CSS variables or CSS Custom Properties limited subset polyfill/shim.
88

99
We strive for the most complete transformation but we/no plugin can achieve true complete parity according to the [speficification](http://dev.w3.org/csswg/css-variables/) because of the DOM cascade unknowns.
1010

11-
## Latest Version: 0.2.3
11+
## Latest Version: v0.3.1
1212
### [Changelog](https://github.com/MadLittleMods/postcss-css-variables/blob/master/CHANGELOG.md)
1313

1414
### Install
@@ -87,6 +87,9 @@ will be processed to:
8787

8888
When using this feature, `postcss-css-variables` will output invalid CSS by itself(but you did input invalid CSS anyway). This feature is best paired with [`postcss-nested`](https://github.com/postcss/postcss-nested) in order to properly expand the rules.
8989

90+
Run `postcss-nested` before `postcss-css-variables` so that `postcss-nested` can properly expand the `&` references before we start resolving variable values.
91+
92+
9093
```js
9194
var postcss = require('postcss');
9295
var cssvariables = require('postcss-css-variables');

0 commit comments

Comments
 (0)