Details

      Description

      We currently have means to render Closure Templates (Soy) in different ways:

      Both mechanisms allow a developer to use Closure Templates an metal to build components and applications, and take care of all the necessary infrastructure to render the template (html) and bootstrap the necessary logic (js).

      Unfortunately, this is not decoupled in a way that can be easily leveraged in other areas of the product where someone would want to use Closure Templates as their rendering template of choice (ADTs, CustomRenderers...)

      By abstracting the logic, in a similar fashion as  JSPRenderer currently does, we could support more advanced usages like:

       

      public String renderSomething(...) {
          String template = "MyComponent.soy");
      
          SoyContext soyContext = SoyContextFactoryUtil.createSoyContext();
      
          soyContext.put("foo", "bar");
      
         return SoyRenderer.render(template, context);
      }

       

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                ivan.zaera Ivan Zaera
                Reporter:
                jose.balsas Chema Balsas
                Recent user:
                Esther Sanz
                Participants of an Issue:
              • Votes:
                0 Vote for this issue
                Watchers:
                4 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Packages

                  Version Package
                  Master