Thanks Dakshika. Will go through the resources.

On Tue, Jan 12, 2016 at 7:42 AM, Dakshika Jayathilaka <[email protected]>
wrote:

> Hi Fazian,
>
> since Jaggery consider as a server side js language you can follow
> standard options that available for js. AFAIK
> we follow google js style guide. [1]
>
> As for tools,
>
> For code sanity check - JSLint [2] or Closure Linter [3]
> Javascript documentation - JSDoc-toolkit [4]
> Unit testing - QUnit [5], JSUnit [6]
>
>
> [1] https://google.github.io/styleguide/javascriptguide.xml
> [2] https://code.google.com/p/jslint4java/
> [3] https://developers.google.com/closure/utilities/
> [4] http://code.google.com/p/jsdoc-toolkit/
> [5] http://docs.jquery.com/QUnit
> [6] http://www.jsunit.net/
>
>
> Regards,
>
> *Dakshika Jayathilaka*
> PMC Member & Committer of Apache Stratos
> Senior Software Engineer
> WSO2, Inc.
> lean.enterprise.middleware
> 0771100911
>
> On Mon, Jan 11, 2016 at 7:59 PM, Fazlan Nazeem <[email protected]> wrote:
>
>> Hi,
>>
>> Is there any guideline documentation on how to format jaggery files or
>> any existing formatter that we could use with sublime/intellij that follows
>> the wso2 standard for formatting jaggery files?
>>
>>
>> --
>> Thanks & Regards,
>>
>> Fazlan Nazeem
>>
>> *Software Engineer*
>>
>> *WSO2 Inc*
>> Mobile : +94772338839
>> <%2B94%20%280%29%20773%20451194>
>> [email protected]
>>
>> _______________________________________________
>> Dev mailing list
>> [email protected]
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>


-- 
Thanks & Regards,

Fazlan Nazeem

*Software Engineer*

*WSO2 Inc*
Mobile : +94772338839
<%2B94%20%280%29%20773%20451194>
[email protected]
_______________________________________________
Dev mailing list
[email protected]
http://wso2.org/cgi-bin/mailman/listinfo/dev

Reply via email to