lint

How do you tell scss-lint to ignore a particular line in a .scss file? i.e. can you do something like this: .example { display: block !important; // sass-lint: ignore } Yep, see the docs on disabling linters via source // scss-lint:disable ImportantRule .example { display: block !important; } // scss-lint:enable ImportantRule Just adding to steveax's great answer : If it's just for the one line, you can directly add the comment there and it will only affect that very line. For instance, consider the following piece of code: .example { display: block !important; // scss-lint:disable

Take a look at this code snippet. I am getting an error with the last line, because I am passing an 'index' instead of a resource. I thought it was a lint issue and tried to suppress it. Then I noticed I am getting this error only when I building for release. It works fine when building for debug. I am totally clueless. Can anyone throw some light into what I am doing wrong. //Get paddingLeft, paddingRight int[] attrsArray = new int[]{ android.R.attr.paddingLeft, // 0 android.R.attr.paddingRight, // 1 }; TypedArray ta = context.obtainStyledAttributes(attrs, attrsArray); if (ta == null) return;

Closed. This question is off-topic. It is not currently accepting answers. Learn more . Want to improve this question? Update the question so it's on-topic for Stack Overflow. Large projects with multiple developers often result in code that is inconsistent in style. I am looking for a lint -like tool tailored to Objective-C that goes beyond the scope of the Clang Static Analyser and checks for adherence to stylistic conventions; e.g. braces, indentation, comment formatting, declaring variables at the top of functions and so on. I am aware of AnalysisTool , but it doesn't quite do what I'm

I use a version switch to support older Android versions. int sdk = Build.VERSION.SDK_INT; if (sdk < Build.VERSION_CODES.HONEYCOMB) { ColorDrawable colorDrawable = new ColorDrawable(shapeColor); //noinspection deprecation viewHolder.shape.setBackgroundDrawable(colorDrawable); } else { viewHolder.shape.setColor(shapeColor); } When build the project with Gradle from the command line the following warning is output by Lint: app/src/main/java/com/example/MyApp/CustomListAdapter.java:92: warning: [deprecation] setBackgroundDrawable(Drawable) in View has been deprecated viewHolder.shape

I know there are already a few questions on this theme here on SO, but very few have accepted answers, and I don't think I have found the exact same problem as mine. I'm building a Swift pod, and in my code I rely on the Google Maps iOS SDK, which is bundled as a .framework file. The project builds OK in Xcode, however I have troubles publishing the lib to Cocoapods. I managed to have a Podspec file that almost validates using the pod lib lint command. However, now that I've added the Google-Maps-iOS-SDK pod as a dependency in the Podspec file, it fails with the following message: $ pod lib

we're currently setting up out integration server and during that process we've set up pre-commit hooks on the SVN so that our developers can't check in files that are syntactically invalid (primarily PHP and XML). We also have a bunch of .sql files (for MySQL) which I'd like to lint as well. Unfortunately, Google didn't turn up anything useful for this task. Any ideas? The commercial version of MySQL Workbench has a syntax checker for MySQL statements, but of course that would only cover the database aspects. See http://mysql.com/products/workbench/ (though I found the factoid in the help

I am trying to get babel-eslint to work on Sublime 3. I have installed: eslint and babel-eslint globally on npm SublimeLinter package on Sublime SublimeLinter-contrib-eslint package on Sublime Also, I have added: "syntax_map": { ... "JavaScript (Babel)": "javascript" } to my SublimeLinter.sublime-settings file. When I run the linter with "parser": "espree" on my .eslintrc file it works fine. But when I change the parser to babel-eslint it stops working. I tried to follow the tutorial here: https://medium.com/@dan_abramov/lint-like-it-s-2015-6987d44c5b48 and I seem to be doing everything

At the moment, I need to ignore a string concatenation warning relative to internationalization, but would like to "learn how to fish" for other specialized warnings in the future. In the tools subfolder from your Android SDK folder, run lint --list Source: http://tools.android.com/tips/lint/suppressing-lint-warnings and scroll down to "Issue Id's" Using the version bundled with android studio 1.5.1 lint --list Valid issue categories: Correctness Correctness:Messages Security Performance Usability:Typography Usability:Icons Usability Accessibility Internationalization Bi-directional Text Valid