This version is not covered by your current version range.
Without accepting this pull request your project will work just like it did before. There might be a bunch of new features, fixes and perf improvements that the maintainers worked on for you though.
I recommend you look into these changes and try to get onto the latest version of bem-xjst.
Given that you have a decent test suite, a passing build is a strong indicator that you can take advantage of these changes by merging the proposed change into your project. Otherwise this branch is a great starting point for you to work on the update.
Do you have any ideas how I could improve these pull requests? Did I report anything you think isn’t right?
Are you unsure about how things are supposed to work?
There is a collection of frequently asked questions and while I’m just a bot, there is a group of people who are happy to teach me new things. Let them know.
Hello lovely humans,
bem-xjst just published its new version 8.5.2.
This version is not covered by your current version range.
Without accepting this pull request your project will work just like it did before. There might be a bunch of new features, fixes and perf improvements that the maintainers worked on for you though.
I recommend you look into these changes and try to get onto the latest version of bem-xjst. Given that you have a decent test suite, a passing build is a strong indicator that you can take advantage of these changes by merging the proposed change into your project. Otherwise this branch is a great starting point for you to work on the update.
Do you have any ideas how I could improve these pull requests? Did I report anything you think isn’t right? Are you unsure about how things are supposed to work?
There is a collection of frequently asked questions and while I’m just a bot, there is a group of people who are happy to teach me new things. Let them know.
Good luck with your project :sparkles:
You rock!
:palm_tree:
GitHub Release
This release is port of v7.6.4.
Fixed bug in BEMTREE: special html field render as it’s value.
Example of BEMJSON:
{ block: 'b1', content: { html: '<br>' } }Render result with v7.6.2 (before fix):
{ block: 'b1', content: '<br>' }.Render result with v7.6.3 (after fix):
{ block: 'b1', content: { html: '<br>' } }.Commits:
f955d4080e] - BEMTREE: special unescaped html field from BEMJSON should render as is (miripiruni)The new version differs by 6 commits .
c54f2f78.5.2d9b3d14update AUTHORSed7fc0echangelog updatedf955d40BEMTREE: special unescaped html field from BEMJSON should render as is7754787Docs: fix spelling66e0206Docs: fixed linksSee the full diff.
This pull request was created by greenkeeper.io.
Tired of seeing this sponsor message? :zap:
greenkeeper upgrade