mirror of
https://github.com/marko-js/marko.git
synced 2025-12-08 19:26:05 +00:00
3.1 KiB
3.1 KiB
Changelog
2.x
2.0.x
2.0.5
- Fixed #36 - Don't use
invokeBody()in the cache taglib
2.0.4
- ❗ Fixed #36 - Deprecated - When using
<include>with body content, nested body content is now passed in asStringproperty namedbody. Old behavior: nested content would be passed in as aFunctionproperty namedinvokeBodythat would return theStringvalue of the nested content.invokeBody()has been deprecated.
2.0.3
- Fixed #36 - Don't use
invokeBody()in test code and the HTML comments tag
2.0.2
- ❗ Fixed #36 - Deprecated
input.invokeBody()in favor ofinput.renderBody(out) - Fixed #37 - Duplicate input property for custom tag renderers
2.0.1
- Fixed #35 - Added support for
<compiler-options>. Example:
<compiler-options whitespace="preserve" />
A
B
C
2.0.0
- Dynamic attributes for scanned tags without a tag will have dashes removed by default.
- ❗ When using
tags-dirto discover tags that do not have amarko-tag.json, the previous behavior was to allow all attributes and to use the actual attribute name as the input property name. For example, when using<hello first-name="John">, first name would need to be read in asinput['first-name']. This was changed such that the first name property should now be read in asinput.firstName(dashes removed and converted to camel case)
- ❗ When using
- Changes to allow UI component to be put into a single JS file:
- Updated taglib directory scanner to use
index.jsif found. New search order:renderer.js(userenderer.jsif it exists)index.js(useindex.jsif it exists and assume it exports arendererorrenderproperty)template.marko(use the template as the renderer if norenderer.jsorindex.js)
- ❗ Changes to the taglib directory scanner could break existing code. Specifically, if a UI component directory had an
index.jsfile and atemplate.markofile then in inmarko@<2thetemplate.markofile would have been selected as the renderer. Inmarko@2.x, theindex.jswill be selected as the tag renderer.
- Updated taglib directory scanner to use
- ❗ Removed support for mapping a tag renderer to a module with a
processmethod - Removed sub-module
marko/rendererthat exports raptor-renderer
1.x
1.6.x
1.6.1
- Added back code to allow the new marko runtime to load templates compiled by an earlier compiler that used
module.exports
1.6.0
- Fixed #32. Switched from
module.exports = function create(__helpers) { ... }toexports.create = function(__helpers) { ... }to avoid circular dependency problems
1.5.x
1.5.8
- Added support for adding "static" code to the top of a compiled template (helpful for initializing variables or running code once).
1.5.7
- Added sub-module
marko/rendererthat exports raptor-renderer
1.5.6
- Changes to avoid unoptimized code in V8
1.5.5
- Handle case where template was loaded before hot-reload was enabled
1.5.4
- Added support for
$globalinrenderSync