All Versions
605
Latest Version
Avg Release Cycle
8 days
Latest Release
728 days ago
Changelog History
Page 48
Changelog History
Page 48
-
v3.7.2 Changes
- ๐ Fixed #328 - Improve error reporting when taglib/tag definition fails to load
- โ Additional change to disable escaping for dynamic
Text
nodes added to body of<script>
tag to fix issue #326
-
v3.7.1 Changes
- ๐ Improved escaping within the
<script>
tag to fix issue #322. Special HTML characters will no longer be escaped within the context of the<script>
tag since browsers do not decode HTML entities within the<script>
tag. Instead, only the ending</script>
tag sequence is escaped using JavaScript string escaping sequences.
- ๐ Improved escaping within the
-
v3.7.0 Changes
- ๐ง Made change to make configuration a true singleton shared across all instances of
marko
loaded at runtime (commit)
- ๐ง Made change to make configuration a true singleton shared across all instances of
-
v3.7.x
-
v3.6.2 Changes
- ๐ Improved support for hot reloading by automatically disabling
assumeUpToDate
if hot reload is enabled. (Pull Request #320 by @ianvonholt)
- ๐ Improved support for hot reloading by automatically disabling
-
v3.6.1 Changes
- ๐ Fixed a bug that was causing transforms to be run on detached nodes. This was manifesting itself in the
<async-fragment>
to<await>
transform if anif()
attribute was present (or other core attributes that end up wrapping the tag it is defined on).
- ๐ Fixed a bug that was causing transforms to be run on detached nodes. This was manifesting itself in the
-
v3.6.0 Changes
- ๐ Introduced a new and simpler
<await>
tag that should be used instead of the now deprecated<async-fragment>
tag (see deprecation details below) (Pull Request #312 by @mlrawlings)
๐ Deprecations
- ๐ Deprecated the
<async-fragment var="<var>" data-provider=<data-provider>>
tag in favor of the<await(<var> from <data-provider>)>
tag:
OLD:
<async-fragment var="userInfo" data-provider=data.userInfoPromise> Hello ${userInfo.name}! </async-fragment>
๐ NEW:
<await(userInfo from data.userInfoPromise)> Hello ${userInfo.name}! </await>
๐ The
<await>
tag supports all of the attributes of the previous<async-fragment>
tag except forvar
anddata-provider
:<await(userInfo from data.userInfoPromise) name="userInfo" timeout=10000 client-reorder> Hello ${userInfo.name}! </await>
โฑ Finally, the nested tags for providing content for the placeholder, error and timeout messages have been renamed accordingly:
<await(userInfo from data.userInfoPromise) client-reorder> <await-placeholder> This is alternate content while the async fragment is loading. </await-placeholder> <await-timeout> A timeout has occurred! </await-timeout> <await-error> A error has occurred! </await-error> Hello ${userInfo.name}! </await>
- ๐ Introduced a new and simpler
-
v3.6.x