soydata.js not defined despite loading soydata.js

[GoogleCodeExporter]

dn reports:
"
I'm using Closure Templates with JavaScript.
I am not using Closure Library.

In my HTML document I included a reference to the soyutils.js that
comes with 'closure-templates-for-javascript-latest.zip'.
If I try to use soy.renderElement I get an error: 'soydata is not
defined'.
I found a soydata.js file, but that one does not define the soydata
object, and furthermore it depends on yet another object/file because
it calls 'goog.provide'.

Is anybody else in a similar situation?
Any hint on how to get the soydata object defined before I indirectly
need it?
"

Original issue reported on code.google.com by mikesamuel@gmail.com on 22 Sep 2011 at 7:50

[GoogleCodeExporter]

I also have the problem, with Closure Templates + Closure Library.

Templates compile from soy to JS fine. Then when Library tries to compile the 
templates, "soydata" and "soydata.SanitizedContentKind" doesn't exist. Neither 
are defined in Closure Library, and "SanitizedContentKind" doesn't even have 
any hits on Google.

mikesamuel -- could you show me where the soydata.js file is, please?

Original comment by mic.t.boyd on 24 Sep 2011 at 4:02

[GoogleCodeExporter]

soydata.js is here:
http://closure-templates.googlecode.com/svn/trunk/javascript/soydata.js

Original comment by mic.t.boyd on 24 Sep 2011 at 4:09

[GoogleCodeExporter]

http://code.google.com/p/closure-templates/source/detail?r=21 gets rid of 
soydata entirely.  The code that was in soydata.js has now been rolled into 
soyutils.js and soyutils_usegoog.js so you only need to include one JS file 
same as before soydata.

Original comment by mikesamuel@gmail.com on 14 Oct 2011 at 7:57

• Changed state: Fixed