2024-02-26-rc1

Full Changelog: https://github.com/yext/closure-templates/commits/2024-02-26

Full Changelog: 2020-08-24...2024-02-26-rc1

20190307-patched-2

Yext patches to Closure templates

Patches:
1. Throw exception on non-nullsafe access on null
2. Treat content of text/template script tags as HTML.
3. SoyErrorKind: do our best to return an error message instead of throwing

This introduces a new TYPE attribute context type, for attributes which specify
a MIME type. This doesn't currently change the rules used to parse the attribute
value (though it could); the value is just consumed as any text
attribute. However, it is examined afterwards and can be used to override the
element type. In this case, instead of retaining the SCRIPT element type that
was set when reading the tag name, the element type is set back to NORMAL for
text/template scripts. This causes the context to shift into HTML_PCDATA instead
of JS after consuming the element start end tag (that is, the contents of the
node will be parsed and escaped as mixed HTML content, not Javascript).

20190307-patched

Yext patches to Closure templates

Patches:
1. Throw exception on non-nullsafe access on null
2. Treat content of text/template script tags as HTML.
3. SoyErrorKind: do our best to return an error message instead of throwing

This introduces a new TYPE attribute context type, for attributes which specify
a MIME type. This doesn't currently change the rules used to parse the attribute
value (though it could); the value is just consumed as any text
attribute. However, it is examined afterwards and can be used to override the
element type. In this case, instead of retaining the SCRIPT element type that
was set when reading the tag name, the element type is set back to NORMAL for
text/template scripts. This causes the context to shift into HTML_PCDATA instead
of JS after consuming the element start end tag (that is, the contents of the
node will be parsed and escaped as mixed HTML content, not Javascript).

2020-08-24

Patched version of the 2020-08-24 upstream closure-templates release.

The patch treats the contents of <script type="text/template"> as a HTML context.

20190307

Pre-built artifacts for the 2019-03-07 release

20170808: Yext patches to Closure templates

Patches:
1. Add PoParser and PoGenerator (com.google.template.soy.pomsgplugin)
2. Throw exception on non-nullsafe access on null
3. Treat content of text/template script tags as HTML.

This introduces a new TYPE attribute context type, for attributes which specify
a MIME type. This doesn't currently change the rules used to parse the attribute
value (though it could); the value is just consumed as any text
attribute. However, it is examined afterwards and can be used to override the
element type. In this case, instead of retaining the SCRIPT element type that
was set when reading the tag name, the element type is set back to NORMAL for
text/template scripts. This causes the context to shift into HTML_PCDATA instead
of JS after consuming the element start end tag (that is, the contents of the
node will be parsed and escaped as mixed HTML content, not Javascript).