-
Notifications
You must be signed in to change notification settings - Fork 29
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #23 from riot/dev
v2.3.12
- Loading branch information
Showing
19 changed files
with
424 additions
and
151 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,41 @@ | ||
# COMPILER CHANGES | ||
|
||
## v2.3.12 | ||
|
||
- Gets rid of the zero-indentation restriction for custom tags, now you can indent these tags, but the opening and closing tag must have exactly the same indentation (length and type). All the tag will be unindented by this amount. | ||
- Support for `src` and `charset` attributes in `<script>` tags for reading JavaScript sources from the file system - [riot#507](https://github.com/riot/riot/issues/507) | ||
- The `compile` function can return separate parts by setting the new `entities` option. These parts has unescaped newlines. | ||
- New attribute `options` for `script` and `style` tags will append/overwrite attributes in the default configuration object of the parser at tag level. | ||
- Fix [riot#1261](https://github.com/riot/riot/issues/1261): `<pre>` tag does not preserve neither `\n` nor `\t`. | ||
Now whitespace within `<pre>` tags is always preserved. | ||
- Fix [riot#1358](https://github.com/riot/riot/issues/1358): Empty style in tag (scoped) breaks. | ||
|
||
## v2.3.11 | ||
|
||
- New type="babel" supports babel-core v6.x. You must `npm install babel-preset-es2015` too, for this works. | ||
Use type="es6" for babel and babel-core v5.8.x and bellow. | ||
- Fix [riot#1306](https://github.com/riot/riot/issues/1306): Compiler preserves newlines in class objects, causing "Unterminated String Constant" errors. | ||
- Fix [riot#1314](https://github.com/riot/riot/issues/1314): `settings.brackets` no longer works. | ||
|
||
## v2.3.0 | ||
|
||
This is a complete rewrite and the first solo version of the compiler. | ||
|
||
- Now the compiler generates a call to the new `riot.tag2` function, with the same parameters as `riot.tag` and an | ||
additional one: the brackets used in the compilation. `riot.tag2` requires all parameters except the brackets, | ||
so the compiler generates all but ignores the brackets if there are no generated expressions. | ||
- Unlike previous versions, backslashes are removed from the expressions (before being sent to any parser). | ||
Outside of expressions, all backslashes are preserved. | ||
- Double quotes inside expressions are converted to `"`, to avoid issues with HTML markup | ||
|
||
- Fix [riot#1207](https://github.com/riot/riot/issues/1207): Riot compiler/parser breaks indentation. | ||
- Fix [riot#1120](https://github.com/riot/riot/issues/1120): Double quotes break Riot attributes | ||
|
||
Enhancements | ||
|
||
- Multiple `<script>` blocks. These can have different types and are merged with the untagged script block, if any. | ||
- More flexible formats in ES6 style method definitions. | ||
- In the JavaScript, trailing whitespace are removed and multiple empty lines are combined into one. | ||
- Better recognition of expressions. Now you can use almost any character, even in unquoted expressions (expressions containing the `>` operator needs to be enclosed in quotes) - [riot#744](https://github.com/riot/riot/issues/744) | ||
- If the first character inside an expression is `^`, the expression is not passed to any parser. This is some sort of type=none at expression level - [riot#543](https://github.com/riot/riot/issues/543) and [riot#1090](https://github.com/riot/riot/issues/1090) | ||
- Type es6 now supports babel-core - [riot#1039](https://github.com/riot/riot/issues/1039) |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.