The onClick attribute value should be the name of a method in this View's context to invoke when the view is clicked. This name must correspond to a public method that takes exactly one parameter of type View.
Must be a string value, using '\;' to escape characters such as '\n' or '\uxxxx' for a unicode character.
Note: This issue has an associated quickfix operation in Android Studio/IntelliJ
Priority: 8 / 10
Category: Correctness
Severity: Error
Explanation: Incompatible Gradle Versions.
There are some combinations of libraries, or tools and libraries, that are incompatible, or can lead to bugs. One such incompatibility is compiling with a version of the Android support libraries that is not the latest version (or in particular, a version lower than your targetSdkVersion.)
312 // Temporary fix until I find a way to handle this efficiently.
313 prefsEditor.putString(websiteData.getString("id"),
314 websiteData.getString("name"));
315prefsEditor.commit(); 316 }
317
376 // Temporary fix until I find a way to handle this efficiently.
377 prefsEditor.putString(websiteData.getString("id"),
378 websiteData.getString("name"));
379prefsEditor.commit(); 380 }
381
Note: This issue has an associated quickfix operation in Android Studio/IntelliJ
Priority: 6 / 10
Category: Correctness
Severity: Warning
Explanation: Missing commit() on SharedPreference editor.
After calling edit() on a SharedPreference, you must call commit() or apply() on the editor to save the results.
This check ensures that a layout resource which is defined in multiple resource folders, specifies the same set of widgets.
This finds cases where you have accidentally forgotten to add a widget to all variations of the layout, which could result in a runtime crash for some resource configurations when a findViewById() fails.
There are cases where this is intentional. For example, you may have a dedicated large tablet layout which adds some extra widgets that are not present in the phone version of the layout. As long as the code accessing the layout resource is careful to handle this properly, it is valid. In that case, you can suppress this lint check for the given extra or missing views, or the whole layout
41 * nnuuneoi's article was a great help by programming the permissions for API 23 and higher.
42 * Article: https://inthecheesefactory.com/blog/things-you-need-to-know-about-android-m-permission-developer-edition
43 */
44 public class BaseActivity extends AppCompatActivity implements NavigationView.OnNavigationItemSelectedListener { 45 46 // Variables used for searching
Priority: 6 / 10
Category: Correctness
Severity: Warning
Explanation: Class is not registered in the manifest.
Activities, services and content providers should be registered in the AndroidManifest.xml file using <activity>, <service> and <provider> tags.
If your activity is simply a parent class intended to be subclassed by other "real" activities, make it an abstract class.
78 79 if(path.canWrite()) {
80 // Create a simple date format to add to the filename.
81 SimpleDateFormat simpleDateFormat = new SimpleDateFormat("dd-MM-yy-kk-mm"); 82 83 String currentDBPath = "/data/" + context.getPackageName() +
Priority: 6 / 10
Category: Correctness
Severity: Warning
Explanation: Implied locale in date format.
Almost all callers should use getDateInstance(), getDateTimeInstance(), or getTimeInstance() to get a ready-made instance of SimpleDateFormat suitable for the user's locale. The main reason you'd create an instance this class directly is because you need to format/parse a specific machine-readable format, in which case you almost certainly want to explicitly ask for US to ensure that you get ASCII digits (rather than, say, Arabic digits).
Therefore, you should either use the form of the SimpleDateFormat constructor where you pass in an explicit locale, such as Locale.US, or use one of the get instance methods, or suppress this error if really know what you are doing.
When inflating a layout, avoid passing in null as the parent view, since otherwise any layout parameters on the root of the inflated layout will be ignored.
Explanation: Incorrect order of elements in manifest.
The <application> tag should appear after the elements which declare which version you need, which features you need, which libraries you need, and so on. In the past there have been subtle bugs (such as themes not getting applied correctly) when the <application> tag appears before some of these other elements, so it's best to order your manifest in the logical dependency order.
Note: This issue has an associated quickfix operation in Android Studio/IntelliJ
Priority: 4 / 10
Category: Correctness
Severity: Warning
Explanation: Obsolete Gradle Dependency.
This detector looks for usages of libraries where the version you are using is not the current stable release. Using older versions is fine, and there are cases where you deliberately want to stick with an older version. However, you may simply not be aware that a more recent version is available, and that is what this lint check helps find.
Note: This issue has an associated quickfix operation in Android Studio/IntelliJ
Priority: 3 / 10
Category: Correctness
Severity: Warning
Explanation: Using dp instead of sp for text sizes.
When setting text sizes, you should normally use sp, or "scale-independent pixels". This is like the dp unit, but it is also scaled by the user's font size preference. It is recommend you use this unit when specifying font sizes, so they will be adjusted for both the screen density and the user's preference.
There are cases where you might need to use dp; typically this happens when the text is in a container with a specific dp-size. This will prevent the text from spilling outside the container. Note however that this means that the user's font size settings are not respected, so consider adjusting the layout itself to be more flexible.
53 <string name="change_rewatched_cancel">Cancel</string>
54 55 <!-- MovieDatabaseHelper -->
56 <string name="write_to_external_storage_as">"Saved as: "</string> 57 <string name="write_to_external_storage_failed">It\'s not possible to write to the external storage.</string>
58 <string name="choose_file">Choose which file to import:</string>
54 55 <!-- MovieDatabaseHelper -->
56 <string name="write_to_external_storage_as">"Saved as: "</string>
57 <string name="write_to_external_storage_failed">It\'s not possible to write to the external storage.</string> 58 <string name="choose_file">Choose which file to import:</string>
59 <string name="import_cancel">Cancel</string>
55 <!-- MovieDatabaseHelper -->
56 <string name="write_to_external_storage_as">"Saved as: "</string>
57 <string name="write_to_external_storage_failed">It\'s not possible to write to the external storage.</string>
58 <string name="choose_file">Choose which file to import:</string> 59 <string name="import_cancel">Cancel</string>
60
56 <string name="write_to_external_storage_as">"Saved as: "</string>
57 <string name="write_to_external_storage_failed">It\'s not possible to write to the external storage.</string>
58 <string name="choose_file">Choose which file to import:</string>
59 <string name="import_cancel">Cancel</string> 60 61 <!-- search_bar -->
Note: This issue has an associated quickfix operation in Eclipse/ADT
Priority: 8 / 10
Category: Correctness:Messages
Severity: Fatal
Explanation: Incomplete translation.
If an application has more than one locale, then all the strings declared in one language should also be translated in all other languages.
If the string should not be translated, you can add the attribute translatable="false" on the <string> element, or you can define all your non-translatable strings in a resource file called donottranslate.xml. Or, you can ignore the issue with a tools:ignore="MissingTranslation" attribute.
By default this detector allows regions of a language to just provide a subset of the strings and fall back to the standard language strings. You can require all regions to provide a full translation by setting the environment variable ANDROID_LINT_COMPLETE_REGIONS.
You can tell lint (and other tools) which language is the default language in your res/values/ folder by specifying tools:locale="languageCode" for the root <resources> element in your resource file. (The tools prefix refers to the namespace declaration http://schemas.android.com/tools.)
../../src/main/AndroidManifest.xml:5: On SDK version 23 and up, your app data will be automatically backed up and restored on app install. Consider adding the attribute android:fullBackupContent to specify an @xml resource which configures which files to backup. More info: https://developer.android.com/training/backup/autosyncapi.html
By default, this flag is set to true. When this flag is set to true, application data can be backed up and restored by the user using adb backup and adb restore.
This may have security consequences for an application. adb backup allows users who have enabled USB debugging to copy application data off of the device. Once backed up, all application data can be read by the user. adb restore allows creation of application data from a source specified by the user. Following a restore, applications should not assume that the data, file permissions, and directory permissions were created by the application itself.
Setting allowBackup="false" opts an application out of both backup and restore.
To fix this warning, decide whether your application should support backup, and explicitly set android:allowBackup=(true|false)".
If not set to false, and if targeting API 23 or later, lint will also warn that you should set android:fullBackupContent to configure auto backup.
388 databaseHelper.onCreate(database);
389 390 // Check if the movie is already in the database.
391 Cursor cursor = database.rawQuery("SELECT * FROM " + 392 MovieDatabaseHelper.TABLE_MOVIES +
393 " WHERE " + MovieDatabaseHelper.COLUMN_MOVIES_ID +
667 dateDialog.setView(dialogView);
668 669 // Set the date for the DatePicker & set the dialog title
670 Cursor cursor = database.rawQuery("SELECT * FROM " + 671 MovieDatabaseHelper.TABLE_MOVIES + " WHERE " +
672 MovieDatabaseHelper.COLUMN_MOVIES_ID + "='" +
787 numberPicker.setMaxValue(9999); // Only set because it is mandatory.
788 789 // Set the default value
790 Cursor cursor = database.rawQuery("SELECT * FROM " + 791 MovieDatabaseHelper.TABLE_MOVIES + " WHERE " +
792 MovieDatabaseHelper.COLUMN_MOVIES_ID + "='" + movieId +
129 130 // Check if it is a movie or a series.
131 try {
132 Cursor cursor = database.rawQuery("SELECT * FROM " + 133 databaseHelper.TABLE_MOVIES + " WHERE " +
134 databaseHelper.COLUMN_MOVIES_ID + "=" +
Priority: 7 / 10
Category: Performance
Severity: Warning
Explanation: Missing recycle() calls.
Many resources, such as TypedArrays, VelocityTrackers, etc., should be recycled (with a recycle() call) after use. This lint check looks for missing recycle() calls.
Note: This issue has an associated quickfix operation in Android Studio/IntelliJ & Eclipse/ADT
Priority: 6 / 10
Category: Performance
Severity: Warning
Explanation: Obsolete layout params.
The given layout_param is not defined for the given layout, meaning it has no effect. This usually happens when you change the parent layout or move view code around without updating the layout params. This will cause useless attribute processing at runtime, and is misleading for others reading the layout so the parameter should be removed.
../../src/main/res/layout/content_cast.xml:7: Possible overdraw: Root element paints background #FFFFFF with a theme that also paints a background (inferred theme is @style/AppTheme_NoActionBar)
../../src/main/res/layout/content_detail.xml:9: Possible overdraw: Root element paints background #FFFFFF with a theme that also paints a background (inferred theme is @style/AppTheme_NoActionBar)
../../src/main/res/layout/content_list.xml:10: Possible overdraw: Root element paints background @color/colorLightGrey with a theme that also paints a background (inferred theme is @style/AppTheme_NoActionBar)
Explanation: Overdraw: Painting regions more than once.
If you set a background drawable on a root view, then you should use a custom theme where the theme background is null. Otherwise, the theme background will be painted first, only to have your custom background completely cover it; this is called "overdraw".
NOTE: This detector relies on figuring out which layouts are associated with which activities based on scanning the Java code, and it's currently doing that using an inexact pattern matching algorithm. Therefore, it can incorrectly conclude which activity the layout is associated with and then wrongly complain that a background-theme is hidden.
If you want your custom background on multiple pages, then you should consider making a custom theme with your custom background and just using that theme instead of a root element background.
Of course it's possible that your custom drawable is translucent and you want it to be mixed with the background. However, you will get better performance if you pre-mix the background with your drawable and use that resulting image or color as a custom theme background instead.
29 <string name="finish_date_unknown">The finish date is not set yet.</string>
30 <string name="times_rewatched">"Times rewatched: "</string>
31 <string name="zero_times_rewatched">Times rewatched: 0</string>
32 <string name="movie_rating">Movie Rating:</string> 33 <string name="movie_rating_ok">OK</string>
34 <string name="movie_not_added_to_list">The movie is not added to the list</string>
../../src/main/res/drawable/ic_menu_tmdb.png: Action Bar icons should use a single gray color (#333333 for light themes (with 60%/30% opacity for enabled/disabled), and #FFFFFF with opacity 80%/30% for dark themes
Priority: 6 / 10
Category: Usability:Icons
Severity: Warning
Explanation: Icon colors do not follow the recommended visual style.
Notification icons and Action Bar icons should only white and shades of gray. See the Android Design Guide for more details. Note that the way Lint decides whether an icon is an action bar icon or a notification icon is based on the filename prefix: ic_menu_ for action bar icons, ic_stat_ for notification icons etc. These correspond to the naming conventions documented in http://developer.android.com/guide/practices/ui_guidelines/icon_design.html
Explanation: Image defined in density-independent drawable folder.
The res/drawable folder is intended for density-independent graphics such as shapes defined in XML. For bitmaps, move it to drawable-mdpi and consider providing higher and lower resolution versions in drawable-ldpi, drawable-hdpi and drawable-xhdpi. If the icon really is density independent (for example a solid color) you can place it in drawable-nodpi.
../../src/main/res/layout/content_detail.xml:115: Buttons in button bars should be borderless; use style="?android:attr/buttonBarButtonStyle" (and ?android:attr/buttonBarStyle on the parent)
../../src/main/res/layout/content_detail.xml:123: Buttons in button bars should be borderless; use style="?android:attr/buttonBarButtonStyle" (and ?android:attr/buttonBarStyle on the parent)
Button bars typically use a borderless style for the buttons. Set the style="?android:attr/buttonBarButtonStyle" attribute on each of the buttons, and set style="?android:attr/buttonBarStyle" on the parent layout
../../src/main/AndroidManifest.xml:5: App is not indexable by Google Search; consider adding at least one Activity with an ACTION-VIEW intent filter. See issue explanation for more details.
Note: This issue has an associated quickfix operation in Android Studio/IntelliJ
Priority: 3 / 10
Category: Usability
Severity: Warning
Explanation: Usage of showAsAction=always
Using showAsAction="always" in menu XML, or MenuItem.SHOW_AS_ACTION_ALWAYS in Java code is usually a deviation from the user interface style guide.Use ifRoom or the corresponding MenuItem.SHOW_AS_ACTION_IF_ROOM instead.
If always is used sparingly there are usually no problems and behavior is roughly equivalent to ifRoom but with preference over other ifRoom items. Using it more than twice in the same menu is a bad idea.
This check looks for menu XML files that contain more than two always actions, or some always actions and no ifRoom actions. In Java code, it looks for projects that contain references to MenuItem.SHOW_AS_ACTION_ALWAYS and no references to MenuItem.SHOW_AS_ACTION_IF_ROOM.
581 // Listen to clicks on the RatingBar.
582 movieRating.setOnTouchListener(new OnTouchListener() {
583 @Override
584 public boolean onTouch(View v, MotionEvent event) { 585 if(event.getAction() == MotionEvent.ACTION_UP) {
586
Priority: 6 / 10
Category: Accessibility
Severity: Warning
Explanation: Accessibility in Custom Views.
If a View that overrides onTouchEvent or uses an OnTouchListener does not also implement performClick and call it when clicks are detected, the View may not handle accessibility actions properly. Logic handling the click actions should ideally be placed in View#performClick as some accessibility services invoke performClick when a click action should occur.
More info:
To suppress this error, use the issue id "ClickableViewAccessibility" as explained in the Suppressing Warnings and Errors section.
Note: This issue has an associated quickfix operation in Android Studio/IntelliJ & Eclipse/ADT
Priority: 3 / 10
Category: Accessibility
Severity: Warning
Explanation: Image without contentDescription
Non-textual widgets like ImageViews and ImageButtons should use the contentDescription attribute to specify a textual description of the widget such that screen readers and other accessibility tools can adequately describe the user interface.
Note that elements in application screens that are purely decorative and do not provide any content or enable a user action should not have accessibility content descriptions. In this case, just suppress the lint warning with a tools:ignore="ContentDescription" attribute.
155 // If the place of birth is different in the new dataset, change it.
156 if(actorObject.has("place_of_birth") && !actorObject.getString("place_of_birth").equals(actorPlaceOfBirth
157 .getText().toString())) {
158 actorPlaceOfBirth.setText(getString(R.string.place_of_birth) + actorObject.getString("place_of_birth")); 159 }
160
161 // If the birthday is different in the new dataset, change it.
162 if(actorObject.has("birthday") && !actorObject.getString("birthday").equals(actorBirthday
163 .getText().toString())) {
164 actorBirthday.setText(getString(R.string.birthday) + actorObject.getString("birthday")); 165 }
166
317 // If the database has an rewatched count, use it, otherwise it is 0.
318 if(cursor.getString(cursor.getColumnIndex(
319 MovieDatabaseHelper.COLUMN_PERSONAL_REWATCHED)) != null) {
320 movieRewatched.setText(getString(R.string.times_rewatched)+ cursor.getString( 321 cursor.getColumnIndex(MovieDatabaseHelper
322 .COLUMN_PERSONAL_REWATCHED)));
When calling TextView#setText
* Never call Number#toString() to format numbers; it will not handle fraction separators and locale-specific digits properly. Consider using String#format with proper format specifications (%d or %f) instead.
* Do not pass a string literal (e.g. "Hello") to display text. Hardcoded text can not be properly translated to other languages. Consider using Android resource strings instead.
* Do not build messages by concatenating text chunks. Such messages can not be properly translated.
Note: This issue has an associated quickfix operation in Eclipse/ADT
Priority: 5 / 10
Category: Internationalization
Severity: Warning
Explanation: Hardcoded text.
Hardcoding text attributes directly in layout files is bad for several reasons:
* When creating configuration variations (for example for landscape or portrait)you have to repeat the actual text (and keep it up to date when making changes)
* The application cannot be translated to other languages by just adding new translations for existing string resources.
There are quickfixes to automatically extract this hardcoded string into a resource lookup.
Priority: 5 / 10
Category: Internationalization:Bidirectional Text
Severity: Warning
Explanation: Using left/right instead of start/end attributes.
Using Gravity#LEFT and Gravity#RIGHT can lead to problems when a layout is rendered in locales where text flows from right to left. Use Gravity#START and Gravity#END instead. Similarly, in XML gravity and layout_gravity attributes, use start rather than left.
For XML attributes such as paddingLeft and layout_marginLeft, use paddingStart and layout_marginStart. NOTE: If your minSdkVersion is less than 17, you should add both the older left/right attributes as well as the new start/right attributes. On older platforms, where RTL is not supported and the start/right attributes are unknown and therefore ignored, you need the older left/right attributes. There is a separate lint check which catches that type of error.
(Note: For Gravity#LEFT and Gravity#START, you can use these constants even when targeting older platforms, because the start bitmask is a superset of the left bitmask. Therefore, you can use gravity="start" rather than gravity="left|start".)
The following issues were not run by lint, either because the check is not enabled by default, or because it was disabled with a command line flag or via one or more lint.xml configuration files in the project directories.
"Other platforms use an explicit back button with label to allow the user to navigate up the application's hierarchy. Instead, Android uses the main action bar's app icon for hierarchical navigation and the navigation bar's back button for temporal navigation."
This check is not very sophisticated (it just looks for buttons with the label "Back"), so it is disabled by default to not trigger on common scenarios like pairs of Back/Next buttons to paginate through screens.
An "easter egg" is code deliberately hidden in the code, both from potential users and even from other developers. This lint check looks for code which looks like it may be hidden from sight.
Accessing a field within the class that defines a getter for that field is at least 3 times faster than calling the getter. For simple getters that do nothing other than return the field, you might want to just reference the local field directly instead.
NOTE: As of Android 2.3 (Gingerbread), this optimization is performed automatically by Dalvik, so there is no need to change your code; this is only relevant if you are targeting older versions of Android.
There are predefined sizes (for each density) for launcher icons. You should follow these conventions to make sure your icons fit in with the overall look of the platform.
The BuildConfig class (available in Tools 17) provides a constant, "DEBUG", which indicates whether the code is being built in release mode or in debug mode. In release mode, you typically want to strip out all the logging calls. Since the compiler will automatically remove all code which is inside a "if (false)" check, surrounding your logging calls with a check for BuildConfig.DEBUG is a good idea.
If you really intend for the logging to be present in release mode, you can suppress this warning with a @SuppressLint annotation for the intentional logging calls.
Note: This issue has an associated quickfix operation in Eclipse/ADT
Disabled By: Default
Priority: 2 / 10
Category: Correctness
Severity: Error
Explanation: Mangled file line endings.
On Windows, line endings are typically recorded as carriage return plus newline: \r\n.
This detector looks for invalid line endings with repeated carriage return characters (without newlines). Previous versions of the ADT plugin could accidentally introduce these into the file, and when editing the file, the editor could produce confusing visual artifacts.
If a class is referenced in the manifest or in a layout file, it must also exist in the project (or in one of the libraries included by the project. This check helps uncover typos in registration names, or attempts to rename or move classes without updating the manifest file properly.
Margin values should be positive. Negative values are generally a sign that you are making assumptions about views surrounding the current one, or may be tempted to turn off child clipping to allow a view to escape its parent. Turning off child clipping to do this not only leads to poor graphical performance, it also results in wrong touch event handling since touch events are based strictly on a chain of parent-rect hit tests. Finally, making assumptions about the size of strings can lead to localization problems.
Note: This issue has an associated quickfix operation in Android Studio/IntelliJ
Disabled By: Default
Priority: 4 / 10
Category: Correctness
Severity: Warning
Explanation: Newer Library Versions Available.
This detector checks with a central repository to see if there are newer versions available for the dependencies used by this project. This is similar to the GradleDependency check, which checks for newer versions available in the Android SDK tools and libraries, but this works with any MavenCentral dependency, and connects to the library every time, which makes it more flexible but also much slower.
More info:
To suppress this error, use the issue id "NewerVersionAvailable" as explained in the Suppressing Warnings and Errors section.
SelectableText
Note: This issue has an associated quickfix operation in Android Studio/IntelliJ
Disabled By: Default
Priority: 7 / 10
Category: Usability
Severity: Warning
Explanation: Dynamic text should probably be selectable.
If a <TextView> is used to display data, the user might want to copy that data and paste it elsewhere. To allow this, the <TextView> should specify android:textIsSelectable="true".
This lint check looks for TextViews which are likely to be displaying data: views whose text is set dynamically. This value will be ignored on platforms older than API 11, so it is okay to set it regardless of your minSdkVersion.
Note: This issue has an associated quickfix operation in Android Studio/IntelliJ
Disabled By: Default
Priority: 10 / 10
Category: Correctness
Severity: Warning
Explanation: Code contains STOPSHIP marker.
Using the comment // STOPSHIP can be used to flag code that is incomplete but checked in. This comment marker can be used to indicate that the code should not be shipped until the issue is addressed, and lint will look for these.
Note: This issue has an associated quickfix operation in Android Studio/IntelliJ & Eclipse/ADT
Disabled By: Default
Priority: 5 / 10
Category: Usability:Typography
Severity: Warning
Explanation: Straight quotes can be replaced with curvy quotes.
Straight single quotes and double quotes, when used as a pair, can be replaced by "curvy quotes" (or directional quotes). This can make the text more readable.
Note that you should never use grave accents and apostrophes to quote, `like this'.
(Also note that you should not use curvy quotes for code fragments.)
This resource id definition appears not to be needed since it is not referenced from anywhere. Having id definitions, even if unused, is not necessarily a bad idea since they make working on layouts and menus easier, so there is not a strong reason to delete these.
Lint errors can be suppressed in a variety of ways:
1. With a @SuppressLint annotation in the Java code
2. With a tools:ignore attribute in the XML file
3. With ignore flags specified in the build.gradle file, as explained below
4. With a lint.xml configuration file in the project
5. With a lint.xml configuration file passed to lint via the --config flag
6. With the --ignore flag passed to lint.
To suppress a lint warning with an annotation, add a @SuppressLint("id") annotation on the class, method or variable declaration closest to the warning instance you want to disable. The id can be one or more issue id's, such as "UnusedResources" or {"UnusedResources","UnusedIds"}, or it can be "all" to suppress all lint warnings in the given scope.
To suppress a lint warning in an XML file, add a tools:ignore="id" attribute on the element containing the error, or one of its surrounding elements. You also need to define the namespace for the tools prefix on the root element in your document, next to the xmlns:android declaration: xmlns:tools="http://schemas.android.com/tools"
To suppress a lint warning in a build.gradle file, add a section like this:
Here we specify a comma separated list of issue id's after the disable command. You can also use warning or error instead of disable to change the severity of issues.
To suppress lint warnings with a configuration XML file, create a file named lint.xml and place it at the root directory of the project in which it applies.
The format of the lint.xml file is something like the following:
<?xml version="1.0" encoding="UTF-8"?>
<lint>
<!-- Disable this given check in this project -->
<issue id="IconMissingDensityFolder" severity="ignore" />
<!-- Ignore the ObsoleteLayoutParam issue in the given files -->
<issue id="ObsoleteLayoutParam">
<ignore path="res/layout/activation.xml" />
<ignore path="res/layout-xlarge/activation.xml" />
</issue>
<!-- Ignore the UselessLeaf issue in the given file -->
<issue id="UselessLeaf">
<ignore path="res/layout/main.xml" />
</issue>
<!-- Change the severity of hardcoded strings to "error" -->
<issue id="HardcodedText" severity="error" />
</lint>
To suppress lint checks from the command line, pass the --ignore flag with a comma separated list of ids to be suppressed, such as: $ lint --ignore UnusedResources,UselessLeaf /my/project/path
OnClick: 
CommitPrefEdits: Missing 
