-
There is a test for changing `mods` in runtime (https://github.com/bem/bem-xjst/blob/master/test/runtime-test.js#L221) but same thing fails for `elemMods`. So this test
``` js
it('should support cha…
-
-
[Here](https://github.com/bem/bem-xjst/blob/master/test/runtime-test.js#L323-L338) is a test which is quite strange:
``` js
it('should restore elemMods', function() {
test(function() {
…
-
http://bem.github.io/bem-xjst/
_bemjson_
```
({
block: 'block',
content: [1,2,3,4,5].map(function() {
return { block: 'ololo' };
})
});
```
_bemhtml_
```
block('ololo').content…
-
`bem-xjst@4.0.1`
BEMJSON:
``` js
[
{
block: 'b1',
mods: { m1: 'v1' }
},
{
block: 'b1',
mods: { ololo: 'trololo' }
}
]
```
Templates:
``` js
block('b…
-
How to reproduce:
``` js
var fs = require('fs'),
bemxjst = require('bem-xjst'), // 4.2.3
uglify = require('uglify-js'), // 2.4.24
bemjson = { block: 'b1' },
tmpl = function() {
…
-
Guess we should add something like this:
---
## `elemMatch()` and `this.elem` changes
There is no sense in `elemMatch()` since you can't test `this.elem` now. (More info?)
## `apply()` behaves sligh…
-
Now:
``` js
block('b1').attrs()(function() {
return this.extend(applyNext(), { a: 'b' })
});
```
Can be wrapped with `block('b1').extendAttrs()({ a: 'b' })`.
-
-
`bem-xjst@1.2.1`
BEMJSON:
``` js
({
block: 'block',
mods: {hello: 'world'},
title: {block: 'i-bem', elem: 'i18n', keyset: 'block', key: 'title'}
});
```
BEMHTML:
``` js
block('block')(…