This is what worked for me: (in your project’s build.gradle) allprojects { gradle.projectsEvaluated { tasks.withType(JavaCompile) { options.compilerArgs << “-Xlint:unchecked” << “-Xlint:deprecation” } } }
The IDE does not know what potential effects your subscription can have when it’s not disposed, so it treats it as potentially unsafe. For example, your Single may contain a network call, which could cause a memory leak if your Activity is abandoned during its execution. A convenient way to manage a large amount of … Read more
You can set your pending intent as val updatedPendingIntent = PendingIntent.getActivity( applicationContext, NOTIFICATION_REQUEST_CODE, updatedIntent, PendingIntent.FLAG_IMMUTABLE or PendingIntent.FLAG_UPDATE_CURRENT // setting the mutability flag ) According to the docs here: https://developer.android.com/about/versions/12/behavior-changes-12#pending-intent-mutability Strongly consider using FLAG_IMMUTABLE, only use FLAG_MUTABLE if some functionality depends on the PendingIntent being mutable, e.g. if it needs to be used with inline replies … Read more
If you are using a relatively recent version of JSHint, the generally preferred approach is to create a .jshintrc file in the root of your project, and put this config in it: { “globals”: { “$”: false } } This declares to JSHint that $ is a global variable, and the false indicates that it … Read more
You can turn off/change a particular rule for a file by putting the configurations at the top of the file. /* eslint no-use-before-define: 0 */ // –> OFF or /* eslint no-use-before-define: 2 */ // –> ON More info
Linting is the process of running a program that will analyse code for potential errors. See lint on wikipedia: lint was the name originally given to a particular program that flagged some suspicious and non-portable constructs (likely to be bugs) in C language source code. The term is now applied generically to tools that flag … Read more