google / google/closure-templates

Documentations and examples are outdated about how to use closure-template in JavaScript

Open
#132 8 comments 3 reactions 0 assignees View on GitHub
Dominant language
Java
Stars
700
Forks
199
Avg merge
2d 12h
Merged PRs (30d)
26

Description

Hi @mikesamuel , @lukesandberg and others ,

My team and I will be very happy if we could use the `soyutils_usegoog.js` file in JavaScript because we are facing some troubles as you can see here #127

**After some investigation in the history of this GitHub repo, I think the reason why `soyutils.js` is missing is because of these two commits :**

1. [Deprecate soyutils.js and recommend the _usegoog version.](https://github.com/google/closure-templates/commit/c67c9de9d61861858f5e2bfd38bb0b4c3dc9bc6f)

2. [Remove the non-Closure version of Soyutils.](https://github.com/google/closure-templates/commit/e74fcfa284a1e31d42ac93e53cb84a71f638c70b)

If I understand good to use closure template in JavaScript we must use `soyutils_usegoog.js`.

**BUT it's impossible to know which files of closure-library must to provide to use closure-template in Javascript.**

Please could you explain and update the documentation on how to use the `soyutils_usegoog.js` version and **what can we have to download on closuse-library repo and which files must be provide to have `soyutils_usegoog.js` to work perfectly ?**

More over, could you update all javascript example in this repo because all of these files use the wrong one and no one can understand the best way to use `soyutils_usegoog.js`

Many thanks.

Contributor guide

Open the contributing guide

Research direction

Start with the JavaScript examples and the documented use of soyutils_usegoog.js; compare them with the two linked history commits and issue #127. Identify which Closure Library files are required, document that setup, and update the JavaScript examples to use the documented approach.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
documentation, frontend
Issue type
Documentation
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.