You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Mar 23, 2024. It is now read-only.
We are using JSCS on our Angular application, but we got some problems with the leadingUnderscoreAccess rule. I let you see the code, JSCS rule and output to see why I say this.
JavaScript demo code:
(function(){angular.module('bug-demo').controller('DemoController',DemoController);DemoController.$inject=['$scope','$log'];functionDemoController($scope,$log){$scope.myFunctionWorking=functionmyFunctionWorking(){$scope.$on('bug',_jscsFailsHereWithJsDocRule)/** * Here is the demonstration that JSCS don't find the @private annotation * * @private **/function_jscsFailsHereWithJsDocRule(){_jscsWillFailEvenWithAccessAnnotation();}/** * Here is the demonstration that JSCS don't find the @access annotation no more * * @access private **/function_jscsWillFailEvenWithAccessAnnotation(){$log.debug('JSCS will report innapropriate error here');}}}})();
/**
* Here is the demonstration that JSCS don't find the @private annotation
*
* @private
*/
function _jscsFailsHereWithJsDocRule()
{
_jscsWillFailEvenWithAccessAnnotation();
}
/**
* Here is the demonstration that JSCS don't find the @access annotation no more
*
* @access private
*/
function _jscsWillFailEvenWithAccessAnnotation()
{
$log.debug('JSCS will report innapropriate error here');
}
I think we should skip checking if there are no correctly formatted jsdoc comment block. Right?
qfox
pushed a commit
to jscs-dev/jscs-jsdoc
that referenced
this issue
Aug 2, 2015
We are using JSCS on our Angular application, but we got some problems with the
leadingUnderscoreAccess
rule. I let you see the code, JSCS rule and output to see why I say this.JavaScript demo code:
.jscrc file used:
Console output – runned with JSCS --verbose:
Running environment:
The text was updated successfully, but these errors were encountered: