Change Details

The #Flow project has yet to experience any issues with LightnCandy as they precompile their templates during development time and write them to disk to be included later, i.e. they don't `eval` the compiled template code and get bitten by T102937. @EBernhardson has provided us with a trimmed down version of the Flow `TemplateParser` class here: https://gist.github.com/anonymous/dd63bccdb955f49a1e76. We need to implement it, test it, and use it in both of the extensions. [] Create the `MobileTemplateParser` class using the gist provided [] Use it in the MobileFrontend extension [] Use it in the Gather extension The Gather change is simple: modify the `Gather\helpers\Template` class to use an instance of `MobileTemplateParser` instead of the `TemplateParser` class. We should adopt a similar approach in the MobileFrontend extension: create a helper class, which abstracts away the templating implementation and, initially, make it use the `MobileTemplateParser`.

The #Flow project has yet to experience any issues with LightnCandy as they precompile their templates during development time and write them to disk to be included later, i.e. they don't `eval` the compiled template code and get bitten by T102937. @EBernhardson has provided us with a trimmed down version of the Flow `TemplateParser` class here: https://gist.github.com/anonymous/dd63bccdb955f49a1e76. We need to implement it, test it, and use it in both of the extensions. [] Create the `MobileTemplateParser` class using the gist provided [] Use it in the MobileFrontend extension [] Use it in the Gather extension The Gather change is simple: modify the `Gather\views\helpers\Template` class to use an instance of `MobileTemplateParser` instead of the `TemplateParser` class. We should adopt a similar approach in the MobileFrontend extension: create a helper class, which abstracts away the templating implementation and, initially, make it use the `MobileTemplateParser`.

The #Flow project has yet to experience any issues with LightnCandy as they precompile their templates during development time and write them to disk to be included later, i.e. they don't `eval` the compiled template code and get bitten by T102937. @EBernhardson has provided us with a trimmed down version of the Flow `TemplateParser` class here: https://gist.github.com/anonymous/dd63bccdb955f49a1e76. We need to implement it, test it, and use it in both of the extensions. [] Create the `MobileTemplateParser` class using the gist provided [] Use it in the MobileFrontend extension [] Use it in the Gather extension The Gather change is simple: modify the `Gather\views\helpers\Template` class to use an instance of `MobileTemplateParser` instead of the `TemplateParser` class. We should adopt a similar approach in the MobileFrontend extension: create a helper class, which abstracts away the templating implementation and, initially, make it use the `MobileTemplateParser`.