When I upload my extension, if it includes files an extension other than the standard .html, .js, .css, .png, etc., those files do not show up in the "My Project" file browser and are not included in the installed extension.
We use Mustache.js for templating and the standard extension for templates is .mustache. If I upload a ZIP containing such files they do not make it through. If I rename them to .mustache.html they do.
Can .mustache be added to the list of approved file extensions please? Alternately, it would be nice to not have an (undocumented) hurdle like this and simply allow files with any extension. (Similar question with no answer here: https://getsatisfaction.com/crossride...)
Help get this topic noticed by sharing it on
Twitter,
Facebook, or email.
Twitter,
Facebook, or email.
-
Hello Eric,
Thanks for your question and apologies for the delay in responding.
Resources supported by our framework are common file suffix's used in extensions. Whilst there are many amazing libraries available that may have their own proprietary file suffixes, using the suffixes does not provide any additional functionality in the context of an extension resource files. Hence, the actual file extension has no particular meaning in this context as the files content must be accessed using appAPI.resources.get. Hence, we recommend renaming the file/s as you mentioned. -
Loading Profile...




EMPLOYEE
