2819 lines
198 KiB
XML
2819 lines
198 KiB
XML
<?xml version="1.0" encoding="UTF-8"?>
|
|
<issues format="6" by="lint 9.2.0">
|
|
|
|
<issue
|
|
id="DefaultLocale"
|
|
severity="Warning"
|
|
message="Implicitly using the default locale is a common source of bugs: Use `toLowerCase(Locale)` instead. For strings meant to be internal use `Locale.ROOT`, otherwise `Locale.getDefault()`."
|
|
category="Correctness"
|
|
priority="6"
|
|
summary="Implied default locale in case conversion"
|
|
explanation="Calling `String#toLowerCase()` or `#toUpperCase()` **without specifying an explicit locale** is a common source of bugs. The reason for that is that those methods will use the current locale on the user's device, and even though the code appears to work correctly when you are developing the app, it will fail in some locales. For example, in the Turkish locale, the uppercase replacement for `i` is **not** `I`.

If you want the methods to just perform ASCII replacement, for example to convert an enum name, call `String#toUpperCase(Locale.ROOT)` instead. If you really want to use the current locale, call `String#toUpperCase(Locale.getDefault())` instead."
|
|
url="https://developer.android.com/reference/java/util/Locale.html#default_locale"
|
|
urls="https://developer.android.com/reference/java/util/Locale.html#default_locale"
|
|
errorLine1=" aVoid -> Toast.makeText(this, "Consulta " + newStatus.toLowerCase(), Toast.LENGTH_SHORT).show())"
|
|
errorLine2=" ~~~~~~~~~~~">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/src/main/java/com/example/medcuida/pro/MainActivity.java"
|
|
line="331"
|
|
column="79"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="DefaultLocale"
|
|
severity="Warning"
|
|
message="Implicitly using the default locale is a common source of bugs: Use `toLowerCase(Locale)` instead. For strings meant to be internal use `Locale.ROOT`, otherwise `Locale.getDefault()`."
|
|
category="Correctness"
|
|
priority="6"
|
|
summary="Implied default locale in case conversion"
|
|
explanation="Calling `String#toLowerCase()` or `#toUpperCase()` **without specifying an explicit locale** is a common source of bugs. The reason for that is that those methods will use the current locale on the user's device, and even though the code appears to work correctly when you are developing the app, it will fail in some locales. For example, in the Turkish locale, the uppercase replacement for `i` is **not** `I`.

If you want the methods to just perform ASCII replacement, for example to convert an enum name, call `String#toUpperCase(Locale.ROOT)` instead. If you really want to use the current locale, call `String#toUpperCase(Locale.getDefault())` instead."
|
|
url="https://developer.android.com/reference/java/util/Locale.html#default_locale"
|
|
urls="https://developer.android.com/reference/java/util/Locale.html#default_locale"
|
|
errorLine1=" && c.getType().toLowerCase().contains(doctorName.toLowerCase().split(" ")[0])) {"
|
|
errorLine2=" ~~~~~~~~~~~">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/src/main/java/com/example/medcuida/pro/MainActivity.java"
|
|
line="433"
|
|
column="52"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="DefaultLocale"
|
|
severity="Warning"
|
|
message="Implicitly using the default locale is a common source of bugs: Use `toLowerCase(Locale)` instead. For strings meant to be internal use `Locale.ROOT`, otherwise `Locale.getDefault()`."
|
|
category="Correctness"
|
|
priority="6"
|
|
summary="Implied default locale in case conversion"
|
|
explanation="Calling `String#toLowerCase()` or `#toUpperCase()` **without specifying an explicit locale** is a common source of bugs. The reason for that is that those methods will use the current locale on the user's device, and even though the code appears to work correctly when you are developing the app, it will fail in some locales. For example, in the Turkish locale, the uppercase replacement for `i` is **not** `I`.

If you want the methods to just perform ASCII replacement, for example to convert an enum name, call `String#toUpperCase(Locale.ROOT)` instead. If you really want to use the current locale, call `String#toUpperCase(Locale.getDefault())` instead."
|
|
url="https://developer.android.com/reference/java/util/Locale.html#default_locale"
|
|
urls="https://developer.android.com/reference/java/util/Locale.html#default_locale"
|
|
errorLine1=" && c.getType().toLowerCase().contains(doctorName.toLowerCase().split(" ")[0])) {"
|
|
errorLine2=" ~~~~~~~~~~~">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/src/main/java/com/example/medcuida/pro/MainActivity.java"
|
|
line="433"
|
|
column="86"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="DefaultLocale"
|
|
severity="Warning"
|
|
message="Implicitly using the default locale is a common source of bugs: Use `toLowerCase(Locale)` instead. For strings meant to be internal use `Locale.ROOT`, otherwise `Locale.getDefault()`."
|
|
category="Correctness"
|
|
priority="6"
|
|
summary="Implied default locale in case conversion"
|
|
explanation="Calling `String#toLowerCase()` or `#toUpperCase()` **without specifying an explicit locale** is a common source of bugs. The reason for that is that those methods will use the current locale on the user's device, and even though the code appears to work correctly when you are developing the app, it will fail in some locales. For example, in the Turkish locale, the uppercase replacement for `i` is **not** `I`.

If you want the methods to just perform ASCII replacement, for example to convert an enum name, call `String#toUpperCase(Locale.ROOT)` instead. If you really want to use the current locale, call `String#toUpperCase(Locale.getDefault())` instead."
|
|
url="https://developer.android.com/reference/java/util/Locale.html#default_locale"
|
|
urls="https://developer.android.com/reference/java/util/Locale.html#default_locale"
|
|
errorLine1=" && c.getType().toLowerCase().contains(doctorName.toLowerCase().split(" ")[0])) {"
|
|
errorLine2=" ~~~~~~~~~~~">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/src/main/java/com/example/medcuida/pro/MainActivity.java"
|
|
line="508"
|
|
column="52"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="DefaultLocale"
|
|
severity="Warning"
|
|
message="Implicitly using the default locale is a common source of bugs: Use `toLowerCase(Locale)` instead. For strings meant to be internal use `Locale.ROOT`, otherwise `Locale.getDefault()`."
|
|
category="Correctness"
|
|
priority="6"
|
|
summary="Implied default locale in case conversion"
|
|
explanation="Calling `String#toLowerCase()` or `#toUpperCase()` **without specifying an explicit locale** is a common source of bugs. The reason for that is that those methods will use the current locale on the user's device, and even though the code appears to work correctly when you are developing the app, it will fail in some locales. For example, in the Turkish locale, the uppercase replacement for `i` is **not** `I`.

If you want the methods to just perform ASCII replacement, for example to convert an enum name, call `String#toUpperCase(Locale.ROOT)` instead. If you really want to use the current locale, call `String#toUpperCase(Locale.getDefault())` instead."
|
|
url="https://developer.android.com/reference/java/util/Locale.html#default_locale"
|
|
urls="https://developer.android.com/reference/java/util/Locale.html#default_locale"
|
|
errorLine1=" && c.getType().toLowerCase().contains(doctorName.toLowerCase().split(" ")[0])) {"
|
|
errorLine2=" ~~~~~~~~~~~">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/src/main/java/com/example/medcuida/pro/MainActivity.java"
|
|
line="508"
|
|
column="86"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="DefaultLocale"
|
|
severity="Warning"
|
|
message="Implicitly using the default locale is a common source of bugs: Use `toLowerCase(Locale)` instead. For strings meant to be internal use `Locale.ROOT`, otherwise `Locale.getDefault()`."
|
|
category="Correctness"
|
|
priority="6"
|
|
summary="Implied default locale in case conversion"
|
|
explanation="Calling `String#toLowerCase()` or `#toUpperCase()` **without specifying an explicit locale** is a common source of bugs. The reason for that is that those methods will use the current locale on the user's device, and even though the code appears to work correctly when you are developing the app, it will fail in some locales. For example, in the Turkish locale, the uppercase replacement for `i` is **not** `I`.

If you want the methods to just perform ASCII replacement, for example to convert an enum name, call `String#toUpperCase(Locale.ROOT)` instead. If you really want to use the current locale, call `String#toUpperCase(Locale.getDefault())` instead."
|
|
url="https://developer.android.com/reference/java/util/Locale.html#default_locale"
|
|
urls="https://developer.android.com/reference/java/util/Locale.html#default_locale"
|
|
errorLine1=" text = text.toLowerCase().trim();"
|
|
errorLine2=" ~~~~~~~~~~~">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/src/main/java/com/example/medcuida/pro/ui/adapters/PacienteAdapter.java"
|
|
line="42"
|
|
column="25"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="DefaultLocale"
|
|
severity="Warning"
|
|
message="Implicitly using the default locale is a common source of bugs: Use `toLowerCase(Locale)` instead. For strings meant to be internal use `Locale.ROOT`, otherwise `Locale.getDefault()`."
|
|
category="Correctness"
|
|
priority="6"
|
|
summary="Implied default locale in case conversion"
|
|
explanation="Calling `String#toLowerCase()` or `#toUpperCase()` **without specifying an explicit locale** is a common source of bugs. The reason for that is that those methods will use the current locale on the user's device, and even though the code appears to work correctly when you are developing the app, it will fail in some locales. For example, in the Turkish locale, the uppercase replacement for `i` is **not** `I`.

If you want the methods to just perform ASCII replacement, for example to convert an enum name, call `String#toUpperCase(Locale.ROOT)` instead. If you really want to use the current locale, call `String#toUpperCase(Locale.getDefault())` instead."
|
|
url="https://developer.android.com/reference/java/util/Locale.html#default_locale"
|
|
urls="https://developer.android.com/reference/java/util/Locale.html#default_locale"
|
|
errorLine1=" if ((item.getNome() != null && item.getNome().toLowerCase().contains(text)) ||"
|
|
errorLine2=" ~~~~~~~~~~~">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/src/main/java/com/example/medcuida/pro/ui/adapters/PacienteAdapter.java"
|
|
line="44"
|
|
column="63"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="DefaultLocale"
|
|
severity="Warning"
|
|
message="Implicitly using the default locale is a common source of bugs: Use `toLowerCase(Locale)` instead. For strings meant to be internal use `Locale.ROOT`, otherwise `Locale.getDefault()`."
|
|
category="Correctness"
|
|
priority="6"
|
|
summary="Implied default locale in case conversion"
|
|
explanation="Calling `String#toLowerCase()` or `#toUpperCase()` **without specifying an explicit locale** is a common source of bugs. The reason for that is that those methods will use the current locale on the user's device, and even though the code appears to work correctly when you are developing the app, it will fail in some locales. For example, in the Turkish locale, the uppercase replacement for `i` is **not** `I`.

If you want the methods to just perform ASCII replacement, for example to convert an enum name, call `String#toUpperCase(Locale.ROOT)` instead. If you really want to use the current locale, call `String#toUpperCase(Locale.getDefault())` instead."
|
|
url="https://developer.android.com/reference/java/util/Locale.html#default_locale"
|
|
urls="https://developer.android.com/reference/java/util/Locale.html#default_locale"
|
|
errorLine1=" (item.getEmail() != null && item.getEmail().toLowerCase().contains(text))) {"
|
|
errorLine2=" ~~~~~~~~~~~">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/src/main/java/com/example/medcuida/pro/ui/adapters/PacienteAdapter.java"
|
|
line="45"
|
|
column="65"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="OldTargetApi"
|
|
severity="Warning"
|
|
message="Not targeting the latest versions of Android; compatibility modes apply. Consider testing and updating this version. Consult the `android.os.Build.VERSION_CODES` javadoc for details."
|
|
category="Correctness"
|
|
priority="6"
|
|
summary="Target SDK attribute is not targeting latest version"
|
|
explanation="When your application or sdk runs on a version of Android that is more recent than your `targetSdk` specifies that it has been tested with, various compatibility modes kick in. This ensures that your application continues to work, but it may look out of place. For example, if the `targetSdk` is less than 14, your app may get an option button in the UI.

To fix this issue, set the `targetSdk` to the highest available value. Then test your app to make sure everything works correctly. You may want to consult the compatibility notes to see what changes apply to each version you are adding support for: https://developer.android.com/reference/android/os/Build.VERSION_CODES.html as well as follow this guide:
https://developer.android.com/distribute/best-practices/develop/target-sdk.html"
|
|
url="https://developer.android.com/distribute/best-practices/develop/target-sdk.html"
|
|
urls="https://developer.android.com/distribute/best-practices/develop/target-sdk.html,https://developer.android.com/reference/android/os/Build.VERSION_CODES.html"
|
|
errorLine1=" targetSdk 35"
|
|
errorLine2=" ~~~~~~~~~~~~">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/build.gradle"
|
|
line="13"
|
|
column="9"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="AndroidGradlePluginVersion"
|
|
severity="Warning"
|
|
message="A newer version of Gradle than 9.4.1 is available: 9.5.0"
|
|
category="Correctness"
|
|
priority="4"
|
|
summary="Obsolete Android Gradle Plugin Version"
|
|
explanation="This detector looks for usage of the Android Gradle Plugin 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."
|
|
errorLine1="distributionUrl=https\://services.gradle.org/distributions/gradle-9.4.1-bin.zip"
|
|
errorLine2=" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/gradle/wrapper/gradle-wrapper.properties"
|
|
line="3"
|
|
column="17"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="GradleDependency"
|
|
severity="Warning"
|
|
message="A newer version of `compileSdk` than 35 is available: 37"
|
|
category="Correctness"
|
|
priority="4"
|
|
summary="Obsolete Gradle Dependency"
|
|
explanation="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."
|
|
errorLine1=" compileSdk 35"
|
|
errorLine2=" ~~~~~~~~~~~~~">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/build.gradle"
|
|
line="8"
|
|
column="5"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="GradleDependency"
|
|
severity="Warning"
|
|
message="A newer version of androidx.appcompat:appcompat than 1.6.1 is available: 1.7.1"
|
|
category="Correctness"
|
|
priority="4"
|
|
summary="Obsolete Gradle Dependency"
|
|
explanation="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."
|
|
errorLine1=" implementation 'androidx.appcompat:appcompat:1.6.1'"
|
|
errorLine2=" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/build.gradle"
|
|
line="39"
|
|
column="20"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="GradleDependency"
|
|
severity="Warning"
|
|
message="A newer version of com.google.android.material:material than 1.11.0 is available: 1.13.0"
|
|
category="Correctness"
|
|
priority="4"
|
|
summary="Obsolete Gradle Dependency"
|
|
explanation="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."
|
|
errorLine1=" implementation 'com.google.android.material:material:1.11.0'"
|
|
errorLine2=" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/build.gradle"
|
|
line="40"
|
|
column="20"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="GradleDependency"
|
|
severity="Warning"
|
|
message="A newer version of androidx.constraintlayout:constraintlayout than 2.1.4 is available: 2.2.1"
|
|
category="Correctness"
|
|
priority="4"
|
|
summary="Obsolete Gradle Dependency"
|
|
explanation="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."
|
|
errorLine1=" implementation 'androidx.constraintlayout:constraintlayout:2.1.4'"
|
|
errorLine2=" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/build.gradle"
|
|
line="41"
|
|
column="20"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="GradleDependency"
|
|
severity="Warning"
|
|
message="A newer version of androidx.lifecycle:lifecycle-livedata-ktx than 2.7.0 is available: 2.10.0"
|
|
category="Correctness"
|
|
priority="4"
|
|
summary="Obsolete Gradle Dependency"
|
|
explanation="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."
|
|
errorLine1=" implementation 'androidx.lifecycle:lifecycle-livedata-ktx:2.7.0'"
|
|
errorLine2=" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/build.gradle"
|
|
line="42"
|
|
column="20"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="GradleDependency"
|
|
severity="Warning"
|
|
message="A newer version of androidx.lifecycle:lifecycle-viewmodel-ktx than 2.7.0 is available: 2.10.0"
|
|
category="Correctness"
|
|
priority="4"
|
|
summary="Obsolete Gradle Dependency"
|
|
explanation="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."
|
|
errorLine1=" implementation 'androidx.lifecycle:lifecycle-viewmodel-ktx:2.7.0'"
|
|
errorLine2=" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/build.gradle"
|
|
line="43"
|
|
column="20"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="GradleDependency"
|
|
severity="Warning"
|
|
message="A newer version of androidx.navigation:navigation-fragment than 2.7.7 is available: 2.9.8"
|
|
category="Correctness"
|
|
priority="4"
|
|
summary="Obsolete Gradle Dependency"
|
|
explanation="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."
|
|
errorLine1=" implementation 'androidx.navigation:navigation-fragment:2.7.7'"
|
|
errorLine2=" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/build.gradle"
|
|
line="44"
|
|
column="20"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="GradleDependency"
|
|
severity="Warning"
|
|
message="A newer version of androidx.navigation:navigation-ui than 2.7.7 is available: 2.9.8"
|
|
category="Correctness"
|
|
priority="4"
|
|
summary="Obsolete Gradle Dependency"
|
|
explanation="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."
|
|
errorLine1=" implementation 'androidx.navigation:navigation-ui:2.7.7'"
|
|
errorLine2=" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/build.gradle"
|
|
line="45"
|
|
column="20"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="GradleDependency"
|
|
severity="Warning"
|
|
message="A newer version of androidx.credentials:credentials than 1.5.0 is available: 1.6.0"
|
|
category="Correctness"
|
|
priority="4"
|
|
summary="Obsolete Gradle Dependency"
|
|
explanation="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."
|
|
errorLine1=" implementation 'androidx.credentials:credentials:1.5.0'"
|
|
errorLine2=" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/build.gradle"
|
|
line="48"
|
|
column="20"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="GradleDependency"
|
|
severity="Warning"
|
|
message="A newer version of androidx.credentials:credentials-play-services-auth than 1.5.0 is available: 1.6.0"
|
|
category="Correctness"
|
|
priority="4"
|
|
summary="Obsolete Gradle Dependency"
|
|
explanation="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."
|
|
errorLine1=" implementation 'androidx.credentials:credentials-play-services-auth:1.5.0'"
|
|
errorLine2=" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/build.gradle"
|
|
line="49"
|
|
column="20"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="GradleDependency"
|
|
severity="Warning"
|
|
message="A newer version of com.google.android.libraries.identity.googleid:googleid than 1.1.1 is available: 1.2.0"
|
|
category="Correctness"
|
|
priority="4"
|
|
summary="Obsolete Gradle Dependency"
|
|
explanation="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."
|
|
errorLine1=" implementation 'com.google.android.libraries.identity.googleid:googleid:1.1.1'"
|
|
errorLine2=" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/build.gradle"
|
|
line="51"
|
|
column="20"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="GradleDependency"
|
|
severity="Warning"
|
|
message="A newer version of androidx.test.ext:junit than 1.1.5 is available: 1.3.0"
|
|
category="Correctness"
|
|
priority="4"
|
|
summary="Obsolete Gradle Dependency"
|
|
explanation="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."
|
|
errorLine1=" androidTestImplementation 'androidx.test.ext:junit:1.1.5'"
|
|
errorLine2=" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/build.gradle"
|
|
line="55"
|
|
column="31"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="GradleDependency"
|
|
severity="Warning"
|
|
message="A newer version of androidx.test.espresso:espresso-core than 3.5.1 is available: 3.7.0"
|
|
category="Correctness"
|
|
priority="4"
|
|
summary="Obsolete Gradle Dependency"
|
|
explanation="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."
|
|
errorLine1=" androidTestImplementation 'androidx.test.espresso:espresso-core:3.5.1'"
|
|
errorLine2=" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/build.gradle"
|
|
line="56"
|
|
column="31"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="GradleDependency"
|
|
severity="Warning"
|
|
message="A newer version of com.google.android.gms:play-services-location than 21.0.1 is available: 21.3.0"
|
|
category="Correctness"
|
|
priority="4"
|
|
summary="Obsolete Gradle Dependency"
|
|
explanation="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."
|
|
errorLine1=" implementation 'com.google.android.gms:play-services-location:21.0.1'"
|
|
errorLine2=" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/build.gradle"
|
|
line="59"
|
|
column="20"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="GradleDependency"
|
|
severity="Warning"
|
|
message="A newer version of com.google.firebase:firebase-bom than 32.7.2 is available: 34.12.0"
|
|
category="Correctness"
|
|
priority="4"
|
|
summary="Obsolete Gradle Dependency"
|
|
explanation="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."
|
|
errorLine1=" implementation platform('com.google.firebase:firebase-bom:32.7.2')"
|
|
errorLine2=" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/build.gradle"
|
|
line="73"
|
|
column="29"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="GradleDynamicVersion"
|
|
severity="Warning"
|
|
message="Avoid using + in version numbers; can lead to unpredictable and unrepeatable builds (com.google.ai.client.generativeai:generativeai:+)"
|
|
category="Correctness"
|
|
priority="4"
|
|
summary="Gradle Dynamic Version"
|
|
explanation="Using `+` in dependencies lets you automatically pick up the latest available version rather than a specific, named version. However, this is not recommended; your builds are not repeatable; you may have tested with a slightly different version than what the build server used. (Using a dynamic version as the major version number is more problematic than using it in the minor version position.)"
|
|
errorLine1=" implementation 'com.google.ai.client.generativeai:generativeai:+'"
|
|
errorLine2=" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/build.gradle"
|
|
line="62"
|
|
column="20"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="NewerVersionAvailable"
|
|
severity="Warning"
|
|
message="A newer version of com.google.guava:guava than 31.1-android is available: 33.6.0-android"
|
|
category="Correctness"
|
|
priority="4"
|
|
summary="Newer Library Versions Available"
|
|
explanation="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."
|
|
errorLine1=" implementation 'com.google.guava:guava:31.1-android'"
|
|
errorLine2=" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/build.gradle"
|
|
line="65"
|
|
column="20"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="NewerVersionAvailable"
|
|
severity="Warning"
|
|
message="A newer version of com.squareup.retrofit2:retrofit than 2.9.0 is available: 3.0.0"
|
|
category="Correctness"
|
|
priority="4"
|
|
summary="Newer Library Versions Available"
|
|
explanation="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."
|
|
errorLine1=" implementation 'com.squareup.retrofit2:retrofit:2.9.0'"
|
|
errorLine2=" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/build.gradle"
|
|
line="68"
|
|
column="20"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="NewerVersionAvailable"
|
|
severity="Warning"
|
|
message="A newer version of com.squareup.retrofit2:converter-gson than 2.9.0 is available: 3.0.0"
|
|
category="Correctness"
|
|
priority="4"
|
|
summary="Newer Library Versions Available"
|
|
explanation="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."
|
|
errorLine1=" implementation 'com.squareup.retrofit2:converter-gson:2.9.0'"
|
|
errorLine2=" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/build.gradle"
|
|
line="69"
|
|
column="20"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="NewerVersionAvailable"
|
|
severity="Warning"
|
|
message="A newer version of com.squareup.okhttp3:okhttp than 4.10.0 is available: 5.3.2"
|
|
category="Correctness"
|
|
priority="4"
|
|
summary="Newer Library Versions Available"
|
|
explanation="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."
|
|
errorLine1=" implementation 'com.squareup.okhttp3:okhttp:4.10.0'"
|
|
errorLine2=" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/build.gradle"
|
|
line="70"
|
|
column="20"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="NewerVersionAvailable"
|
|
severity="Warning"
|
|
message="A newer version of com.github.bumptech.glide:glide than 4.16.0 is available: 5.0.7"
|
|
category="Correctness"
|
|
priority="4"
|
|
summary="Newer Library Versions Available"
|
|
explanation="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."
|
|
errorLine1=" implementation 'com.github.bumptech.glide:glide:4.16.0'"
|
|
errorLine2=" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/build.gradle"
|
|
line="81"
|
|
column="20"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="NewerVersionAvailable"
|
|
severity="Warning"
|
|
message="A newer version of com.github.bumptech.glide:compiler than 4.16.0 is available: 5.0.7"
|
|
category="Correctness"
|
|
priority="4"
|
|
summary="Newer Library Versions Available"
|
|
explanation="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."
|
|
errorLine1=" annotationProcessor 'com.github.bumptech.glide:compiler:4.16.0'"
|
|
errorLine2=" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/build.gradle"
|
|
line="82"
|
|
column="25"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="NotifyDataSetChanged"
|
|
severity="Warning"
|
|
message="It will always be more efficient to use more specific change events if you can. Rely on `notifyDataSetChanged` as a last resort."
|
|
category="Performance"
|
|
priority="8"
|
|
summary="Invalidating All RecyclerView Data"
|
|
explanation="The `RecyclerView` adapter's `onNotifyDataSetChanged` method does not specify what about the data set has changed, forcing any observers to assume that all existing items and structure may no longer be valid. `LayoutManager`s will be forced to fully rebind and relayout all visible views."
|
|
errorLine1=" notifyDataSetChanged();"
|
|
errorLine2=" ~~~~~~~~~~~~~~~~~~~~~~">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/src/main/java/com/example/medcuida/pro/ui/adapters/ConsultaAdapter.java"
|
|
line="40"
|
|
column="9"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="NotifyDataSetChanged"
|
|
severity="Warning"
|
|
message="It will always be more efficient to use more specific change events if you can. Rely on `notifyDataSetChanged` as a last resort."
|
|
category="Performance"
|
|
priority="8"
|
|
summary="Invalidating All RecyclerView Data"
|
|
explanation="The `RecyclerView` adapter's `onNotifyDataSetChanged` method does not specify what about the data set has changed, forcing any observers to assume that all existing items and structure may no longer be valid. `LayoutManager`s will be forced to fully rebind and relayout all visible views."
|
|
errorLine1=" notifyDataSetChanged();"
|
|
errorLine2=" ~~~~~~~~~~~~~~~~~~~~~~">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/src/main/java/com/example/medcuida/pro/ui/adapters/PacienteAdapter.java"
|
|
line="34"
|
|
column="9"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="NotifyDataSetChanged"
|
|
severity="Warning"
|
|
message="It will always be more efficient to use more specific change events if you can. Rely on `notifyDataSetChanged` as a last resort."
|
|
category="Performance"
|
|
priority="8"
|
|
summary="Invalidating All RecyclerView Data"
|
|
explanation="The `RecyclerView` adapter's `onNotifyDataSetChanged` method does not specify what about the data set has changed, forcing any observers to assume that all existing items and structure may no longer be valid. `LayoutManager`s will be forced to fully rebind and relayout all visible views."
|
|
errorLine1=" notifyDataSetChanged();"
|
|
errorLine2=" ~~~~~~~~~~~~~~~~~~~~~~">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/src/main/java/com/example/medcuida/pro/ui/adapters/PacienteAdapter.java"
|
|
line="50"
|
|
column="9"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="DisableBaselineAlignment"
|
|
severity="Warning"
|
|
message="Set `android:baselineAligned="false"` on this element for better performance"
|
|
category="Performance"
|
|
priority="3"
|
|
summary="Missing `baselineAligned` attribute"
|
|
explanation="When a `LinearLayout` is used to distribute the space proportionally between nested layouts, the baseline alignment property should be turned off to make the layout computation faster."
|
|
errorLine1=" <LinearLayout"
|
|
errorLine2=" ~~~~~~~~~~~~">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/src/main/res/layout/activity_editar_perfil.xml"
|
|
line="107"
|
|
column="10"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="Overdraw"
|
|
severity="Warning"
|
|
message="Possible overdraw: Root element paints background `@color/background_color` with a theme that also paints a background (inferred theme is `@style/Theme.Cuida`)"
|
|
category="Performance"
|
|
priority="3"
|
|
summary="Overdraw: Painting regions more than once"
|
|
explanation="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."
|
|
errorLine1=" android:background="@color/background_color""
|
|
errorLine2=" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/src/main/res/layout/activity_detalhe_paciente.xml"
|
|
line="7"
|
|
column="5"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="Overdraw"
|
|
severity="Warning"
|
|
message="Possible overdraw: Root element paints background `#FAFAFA` with a theme that also paints a background (inferred theme is `@style/Theme.Cuida`)"
|
|
category="Performance"
|
|
priority="3"
|
|
summary="Overdraw: Painting regions more than once"
|
|
explanation="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."
|
|
errorLine1=" android:background="#FAFAFA">"
|
|
errorLine2=" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/src/main/res/layout/activity_editar_perfil.xml"
|
|
line="7"
|
|
column="5"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="Overdraw"
|
|
severity="Warning"
|
|
message="Possible overdraw: Root element paints background `@color/background_color` with a theme that also paints a background (inferred theme is `@style/Theme.Cuida`)"
|
|
category="Performance"
|
|
priority="3"
|
|
summary="Overdraw: Painting regions more than once"
|
|
explanation="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."
|
|
errorLine1=" android:background="@color/background_color">"
|
|
errorLine2=" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/src/main/res/layout/activity_forgot_password.xml"
|
|
line="8"
|
|
column="5"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="Overdraw"
|
|
severity="Warning"
|
|
message="Possible overdraw: Root element paints background `@color/background_color` with a theme that also paints a background (inferred theme is `@style/Theme.Cuida`)"
|
|
category="Performance"
|
|
priority="3"
|
|
summary="Overdraw: Painting regions more than once"
|
|
explanation="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."
|
|
errorLine1=" android:background="@color/background_color">"
|
|
errorLine2=" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/src/main/res/layout/activity_login.xml"
|
|
line="7"
|
|
column="5"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="Overdraw"
|
|
severity="Warning"
|
|
message="Possible overdraw: Root element paints background `@color/background_color` with a theme that also paints a background (inferred theme is `@style/Theme.Cuida`)"
|
|
category="Performance"
|
|
priority="3"
|
|
summary="Overdraw: Painting regions more than once"
|
|
explanation="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."
|
|
errorLine1=" android:background="@color/background_color">"
|
|
errorLine2=" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/src/main/res/layout/activity_main.xml"
|
|
line="6"
|
|
column="5"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="Overdraw"
|
|
severity="Warning"
|
|
message="Possible overdraw: Root element paints background `@color/background_color` with a theme that also paints a background (inferred theme is `@style/Theme.Cuida`)"
|
|
category="Performance"
|
|
priority="3"
|
|
summary="Overdraw: Painting regions more than once"
|
|
explanation="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."
|
|
errorLine1=" android:background="@color/background_color">"
|
|
errorLine2=" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/src/main/res/layout/activity_register.xml"
|
|
line="7"
|
|
column="5"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="UnusedResources"
|
|
severity="Warning"
|
|
message="The resource `R.menu.bottom_nav_menu` appears to be unused"
|
|
category="Performance"
|
|
priority="3"
|
|
summary="Unused resources"
|
|
explanation="Unused resources make applications larger and slow down builds.


The unused resource check can ignore tests. If you want to include resources that are only referenced from tests, consider packaging them in a test source set instead.

You can include test sources in the unused resource check by setting the system property `lint.unused-resources.include-tests=true`, and to exclude them (usually for performance reasons), use `lint.unused-resources.exclude-tests=true`.
"
|
|
errorLine1="<menu xmlns:android="http://schemas.android.com/apk/res/android">"
|
|
errorLine2="^">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/src/main/res/menu/bottom_nav_menu.xml"
|
|
line="2"
|
|
column="1"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="UnusedResources"
|
|
severity="Warning"
|
|
message="The resource `R.drawable.btn_outline_error` appears to be unused"
|
|
category="Performance"
|
|
priority="3"
|
|
summary="Unused resources"
|
|
explanation="Unused resources make applications larger and slow down builds.


The unused resource check can ignore tests. If you want to include resources that are only referenced from tests, consider packaging them in a test source set instead.

You can include test sources in the unused resource check by setting the system property `lint.unused-resources.include-tests=true`, and to exclude them (usually for performance reasons), use `lint.unused-resources.exclude-tests=true`.
"
|
|
errorLine1="<ripple xmlns:android="http://schemas.android.com/apk/res/android""
|
|
errorLine2="^">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/src/main/res/drawable/btn_outline_error.xml"
|
|
line="2"
|
|
column="1"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="UnusedResources"
|
|
severity="Warning"
|
|
message="The resource `R.drawable.btn_outline_primary` appears to be unused"
|
|
category="Performance"
|
|
priority="3"
|
|
summary="Unused resources"
|
|
explanation="Unused resources make applications larger and slow down builds.


The unused resource check can ignore tests. If you want to include resources that are only referenced from tests, consider packaging them in a test source set instead.

You can include test sources in the unused resource check by setting the system property `lint.unused-resources.include-tests=true`, and to exclude them (usually for performance reasons), use `lint.unused-resources.exclude-tests=true`.
"
|
|
errorLine1="<shape xmlns:android="http://schemas.android.com/apk/res/android">"
|
|
errorLine2="^">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/src/main/res/drawable/btn_outline_primary.xml"
|
|
line="2"
|
|
column="1"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="UnusedResources"
|
|
severity="Warning"
|
|
message="The resource `R.drawable.circle_bg_large` appears to be unused"
|
|
category="Performance"
|
|
priority="3"
|
|
summary="Unused resources"
|
|
explanation="Unused resources make applications larger and slow down builds.


The unused resource check can ignore tests. If you want to include resources that are only referenced from tests, consider packaging them in a test source set instead.

You can include test sources in the unused resource check by setting the system property `lint.unused-resources.include-tests=true`, and to exclude them (usually for performance reasons), use `lint.unused-resources.exclude-tests=true`.
"
|
|
errorLine1="<shape xmlns:android="http://schemas.android.com/apk/res/android""
|
|
errorLine2="^">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/src/main/res/drawable/circle_bg_large.xml"
|
|
line="2"
|
|
column="1"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="UnusedResources"
|
|
severity="Warning"
|
|
message="The resource `R.color.purple_200` appears to be unused"
|
|
category="Performance"
|
|
priority="3"
|
|
summary="Unused resources"
|
|
explanation="Unused resources make applications larger and slow down builds.


The unused resource check can ignore tests. If you want to include resources that are only referenced from tests, consider packaging them in a test source set instead.

You can include test sources in the unused resource check by setting the system property `lint.unused-resources.include-tests=true`, and to exclude them (usually for performance reasons), use `lint.unused-resources.exclude-tests=true`.
"
|
|
errorLine1=" <color name="purple_200">#93C5FD</color>"
|
|
errorLine2=" ~~~~~~~~~~~~~~~~~">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/src/main/res/values/colors.xml"
|
|
line="18"
|
|
column="12"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="UnusedResources"
|
|
severity="Warning"
|
|
message="The resource `R.color.purple_500` appears to be unused"
|
|
category="Performance"
|
|
priority="3"
|
|
summary="Unused resources"
|
|
explanation="Unused resources make applications larger and slow down builds.


The unused resource check can ignore tests. If you want to include resources that are only referenced from tests, consider packaging them in a test source set instead.

You can include test sources in the unused resource check by setting the system property `lint.unused-resources.include-tests=true`, and to exclude them (usually for performance reasons), use `lint.unused-resources.exclude-tests=true`.
"
|
|
errorLine1=" <color name="purple_500">#3B82F6</color>"
|
|
errorLine2=" ~~~~~~~~~~~~~~~~~">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/src/main/res/values/colors.xml"
|
|
line="19"
|
|
column="12"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="UnusedResources"
|
|
severity="Warning"
|
|
message="The resource `R.color.purple_700` appears to be unused"
|
|
category="Performance"
|
|
priority="3"
|
|
summary="Unused resources"
|
|
explanation="Unused resources make applications larger and slow down builds.


The unused resource check can ignore tests. If you want to include resources that are only referenced from tests, consider packaging them in a test source set instead.

You can include test sources in the unused resource check by setting the system property `lint.unused-resources.include-tests=true`, and to exclude them (usually for performance reasons), use `lint.unused-resources.exclude-tests=true`.
"
|
|
errorLine1=" <color name="purple_700">#1D4ED8</color>"
|
|
errorLine2=" ~~~~~~~~~~~~~~~~~">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/src/main/res/values/colors.xml"
|
|
line="20"
|
|
column="12"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="UnusedResources"
|
|
severity="Warning"
|
|
message="The resource `R.color.teal_200` appears to be unused"
|
|
category="Performance"
|
|
priority="3"
|
|
summary="Unused resources"
|
|
explanation="Unused resources make applications larger and slow down builds.


The unused resource check can ignore tests. If you want to include resources that are only referenced from tests, consider packaging them in a test source set instead.

You can include test sources in the unused resource check by setting the system property `lint.unused-resources.include-tests=true`, and to exclude them (usually for performance reasons), use `lint.unused-resources.exclude-tests=true`.
"
|
|
errorLine1=" <color name="teal_200">#60A5FA</color>"
|
|
errorLine2=" ~~~~~~~~~~~~~~~">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/src/main/res/values/colors.xml"
|
|
line="21"
|
|
column="12"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="UnusedResources"
|
|
severity="Warning"
|
|
message="The resource `R.color.teal_700` appears to be unused"
|
|
category="Performance"
|
|
priority="3"
|
|
summary="Unused resources"
|
|
explanation="Unused resources make applications larger and slow down builds.


The unused resource check can ignore tests. If you want to include resources that are only referenced from tests, consider packaging them in a test source set instead.

You can include test sources in the unused resource check by setting the system property `lint.unused-resources.include-tests=true`, and to exclude them (usually for performance reasons), use `lint.unused-resources.exclude-tests=true`.
"
|
|
errorLine1=" <color name="teal_700">#1E40AF</color>"
|
|
errorLine2=" ~~~~~~~~~~~~~~~">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/src/main/res/values/colors.xml"
|
|
line="22"
|
|
column="12"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="UnusedResources"
|
|
severity="Warning"
|
|
message="The resource `R.color.black` appears to be unused"
|
|
category="Performance"
|
|
priority="3"
|
|
summary="Unused resources"
|
|
explanation="Unused resources make applications larger and slow down builds.


The unused resource check can ignore tests. If you want to include resources that are only referenced from tests, consider packaging them in a test source set instead.

You can include test sources in the unused resource check by setting the system property `lint.unused-resources.include-tests=true`, and to exclude them (usually for performance reasons), use `lint.unused-resources.exclude-tests=true`.
"
|
|
errorLine1=" <color name="black">#000000</color>"
|
|
errorLine2=" ~~~~~~~~~~~~">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/src/main/res/values/colors.xml"
|
|
line="23"
|
|
column="12"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="UnusedResources"
|
|
severity="Warning"
|
|
message="The resource `R.layout.dialog_change_password` appears to be unused"
|
|
category="Performance"
|
|
priority="3"
|
|
summary="Unused resources"
|
|
explanation="Unused resources make applications larger and slow down builds.


The unused resource check can ignore tests. If you want to include resources that are only referenced from tests, consider packaging them in a test source set instead.

You can include test sources in the unused resource check by setting the system property `lint.unused-resources.include-tests=true`, and to exclude them (usually for performance reasons), use `lint.unused-resources.exclude-tests=true`.
"
|
|
errorLine1="<LinearLayout xmlns:android="http://schemas.android.com/apk/res/android""
|
|
errorLine2="^">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/src/main/res/layout/dialog_change_password.xml"
|
|
line="2"
|
|
column="1"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="UnusedResources"
|
|
severity="Warning"
|
|
message="The resource `R.drawable.ic_launcher` appears to be unused"
|
|
category="Performance"
|
|
priority="3"
|
|
summary="Unused resources"
|
|
explanation="Unused resources make applications larger and slow down builds.


The unused resource check can ignore tests. If you want to include resources that are only referenced from tests, consider packaging them in a test source set instead.

You can include test sources in the unused resource check by setting the system property `lint.unused-resources.include-tests=true`, and to exclude them (usually for performance reasons), use `lint.unused-resources.exclude-tests=true`.
"
|
|
errorLine1="<vector xmlns:android="http://schemas.android.com/apk/res/android""
|
|
errorLine2="^">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/src/main/res/drawable/ic_launcher.xml"
|
|
line="1"
|
|
column="1"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="UnusedResources"
|
|
severity="Warning"
|
|
message="The resource `R.drawable.ic_launcher_final` appears to be unused"
|
|
category="Performance"
|
|
priority="3"
|
|
summary="Unused resources"
|
|
explanation="Unused resources make applications larger and slow down builds.


The unused resource check can ignore tests. If you want to include resources that are only referenced from tests, consider packaging them in a test source set instead.

You can include test sources in the unused resource check by setting the system property `lint.unused-resources.include-tests=true`, and to exclude them (usually for performance reasons), use `lint.unused-resources.exclude-tests=true`.
"
|
|
errorLine1="<layer-list xmlns:android="http://schemas.android.com/apk/res/android">"
|
|
errorLine2="^">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/src/main/res/drawable/ic_launcher_final.xml"
|
|
line="2"
|
|
column="1"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="UnusedResources"
|
|
severity="Warning"
|
|
message="The resource `R.drawable.ic_launcher_round` appears to be unused"
|
|
category="Performance"
|
|
priority="3"
|
|
summary="Unused resources"
|
|
explanation="Unused resources make applications larger and slow down builds.


The unused resource check can ignore tests. If you want to include resources that are only referenced from tests, consider packaging them in a test source set instead.

You can include test sources in the unused resource check by setting the system property `lint.unused-resources.include-tests=true`, and to exclude them (usually for performance reasons), use `lint.unused-resources.exclude-tests=true`.
"
|
|
errorLine1="<vector xmlns:android="http://schemas.android.com/apk/res/android""
|
|
errorLine2="^">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/src/main/res/drawable/ic_launcher_round.xml"
|
|
line="1"
|
|
column="1"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="UnusedResources"
|
|
severity="Warning"
|
|
message="The resource `R.drawable.ic_logo` appears to be unused"
|
|
category="Performance"
|
|
priority="3"
|
|
summary="Unused resources"
|
|
explanation="Unused resources make applications larger and slow down builds.


The unused resource check can ignore tests. If you want to include resources that are only referenced from tests, consider packaging them in a test source set instead.

You can include test sources in the unused resource check by setting the system property `lint.unused-resources.include-tests=true`, and to exclude them (usually for performance reasons), use `lint.unused-resources.exclude-tests=true`.
">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/src/main/res/drawable/ic_logo.png"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="UnusedResources"
|
|
severity="Warning"
|
|
message="The resource `R.drawable.ic_logo_scaled` appears to be unused"
|
|
category="Performance"
|
|
priority="3"
|
|
summary="Unused resources"
|
|
explanation="Unused resources make applications larger and slow down builds.


The unused resource check can ignore tests. If you want to include resources that are only referenced from tests, consider packaging them in a test source set instead.

You can include test sources in the unused resource check by setting the system property `lint.unused-resources.include-tests=true`, and to exclude them (usually for performance reasons), use `lint.unused-resources.exclude-tests=true`.
"
|
|
errorLine1="<layer-list xmlns:android="http://schemas.android.com/apk/res/android">"
|
|
errorLine2="^">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/src/main/res/drawable/ic_logo_scaled.xml"
|
|
line="2"
|
|
column="1"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="UnusedResources"
|
|
severity="Warning"
|
|
message="The resource `R.drawable.ic_nav_contactos` appears to be unused"
|
|
category="Performance"
|
|
priority="3"
|
|
summary="Unused resources"
|
|
explanation="Unused resources make applications larger and slow down builds.


The unused resource check can ignore tests. If you want to include resources that are only referenced from tests, consider packaging them in a test source set instead.

You can include test sources in the unused resource check by setting the system property `lint.unused-resources.include-tests=true`, and to exclude them (usually for performance reasons), use `lint.unused-resources.exclude-tests=true`.
"
|
|
errorLine1="<vector xmlns:android="http://schemas.android.com/apk/res/android""
|
|
errorLine2="^">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/src/main/res/drawable/ic_nav_contactos.xml"
|
|
line="1"
|
|
column="1"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="UnusedResources"
|
|
severity="Warning"
|
|
message="The resource `R.drawable.ic_placeholder` appears to be unused"
|
|
category="Performance"
|
|
priority="3"
|
|
summary="Unused resources"
|
|
explanation="Unused resources make applications larger and slow down builds.


The unused resource check can ignore tests. If you want to include resources that are only referenced from tests, consider packaging them in a test source set instead.

You can include test sources in the unused resource check by setting the system property `lint.unused-resources.include-tests=true`, and to exclude them (usually for performance reasons), use `lint.unused-resources.exclude-tests=true`.
"
|
|
errorLine1="<vector xmlns:android="http://schemas.android.com/apk/res/android""
|
|
errorLine2="^">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/src/main/res/drawable/ic_placeholder.xml"
|
|
line="1"
|
|
column="1"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="UnusedResources"
|
|
severity="Warning"
|
|
message="The resource `R.navigation.mobile_navigation` appears to be unused"
|
|
category="Performance"
|
|
priority="3"
|
|
summary="Unused resources"
|
|
explanation="Unused resources make applications larger and slow down builds.


The unused resource check can ignore tests. If you want to include resources that are only referenced from tests, consider packaging them in a test source set instead.

You can include test sources in the unused resource check by setting the system property `lint.unused-resources.include-tests=true`, and to exclude them (usually for performance reasons), use `lint.unused-resources.exclude-tests=true`.
"
|
|
errorLine1="<navigation xmlns:android="http://schemas.android.com/apk/res/android""
|
|
errorLine2="^">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/src/main/res/navigation/mobile_navigation.xml"
|
|
line="2"
|
|
column="1"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="UnusedResources"
|
|
severity="Warning"
|
|
message="The resource `R.string.title_home` appears to be unused"
|
|
category="Performance"
|
|
priority="3"
|
|
summary="Unused resources"
|
|
explanation="Unused resources make applications larger and slow down builds.


The unused resource check can ignore tests. If you want to include resources that are only referenced from tests, consider packaging them in a test source set instead.

You can include test sources in the unused resource check by setting the system property `lint.unused-resources.include-tests=true`, and to exclude them (usually for performance reasons), use `lint.unused-resources.exclude-tests=true`.
"
|
|
errorLine1=" <string name="title_home">Início</string>"
|
|
errorLine2=" ~~~~~~~~~~~~~~~~~">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/src/main/res/values/strings.xml"
|
|
line="3"
|
|
column="13"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="UnusedResources"
|
|
severity="Warning"
|
|
message="The resource `R.string.title_appointments` appears to be unused"
|
|
category="Performance"
|
|
priority="3"
|
|
summary="Unused resources"
|
|
explanation="Unused resources make applications larger and slow down builds.


The unused resource check can ignore tests. If you want to include resources that are only referenced from tests, consider packaging them in a test source set instead.

You can include test sources in the unused resource check by setting the system property `lint.unused-resources.include-tests=true`, and to exclude them (usually for performance reasons), use `lint.unused-resources.exclude-tests=true`.
"
|
|
errorLine1=" <string name="title_appointments">Consultas</string>"
|
|
errorLine2=" ~~~~~~~~~~~~~~~~~~~~~~~~~">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/src/main/res/values/strings.xml"
|
|
line="4"
|
|
column="13"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="UnusedResources"
|
|
severity="Warning"
|
|
message="The resource `R.string.title_medication` appears to be unused"
|
|
category="Performance"
|
|
priority="3"
|
|
summary="Unused resources"
|
|
explanation="Unused resources make applications larger and slow down builds.


The unused resource check can ignore tests. If you want to include resources that are only referenced from tests, consider packaging them in a test source set instead.

You can include test sources in the unused resource check by setting the system property `lint.unused-resources.include-tests=true`, and to exclude them (usually for performance reasons), use `lint.unused-resources.exclude-tests=true`.
"
|
|
errorLine1=" <string name="title_medication">Medicação</string>"
|
|
errorLine2=" ~~~~~~~~~~~~~~~~~~~~~~~">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/src/main/res/values/strings.xml"
|
|
line="5"
|
|
column="13"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="UnusedResources"
|
|
severity="Warning"
|
|
message="The resource `R.string.title_sns24` appears to be unused"
|
|
category="Performance"
|
|
priority="3"
|
|
summary="Unused resources"
|
|
explanation="Unused resources make applications larger and slow down builds.


The unused resource check can ignore tests. If you want to include resources that are only referenced from tests, consider packaging them in a test source set instead.

You can include test sources in the unused resource check by setting the system property `lint.unused-resources.include-tests=true`, and to exclude them (usually for performance reasons), use `lint.unused-resources.exclude-tests=true`.
"
|
|
errorLine1=" <string name="title_sns24">SNS 24</string>"
|
|
errorLine2=" ~~~~~~~~~~~~~~~~~~">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/src/main/res/values/strings.xml"
|
|
line="6"
|
|
column="13"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="UnusedResources"
|
|
severity="Warning"
|
|
message="The resource `R.string.title_profile` appears to be unused"
|
|
category="Performance"
|
|
priority="3"
|
|
summary="Unused resources"
|
|
explanation="Unused resources make applications larger and slow down builds.


The unused resource check can ignore tests. If you want to include resources that are only referenced from tests, consider packaging them in a test source set instead.

You can include test sources in the unused resource check by setting the system property `lint.unused-resources.include-tests=true`, and to exclude them (usually for performance reasons), use `lint.unused-resources.exclude-tests=true`.
"
|
|
errorLine1=" <string name="title_profile">Perfil</string>"
|
|
errorLine2=" ~~~~~~~~~~~~~~~~~~~~">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/src/main/res/values/strings.xml"
|
|
line="7"
|
|
column="13"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="UnusedResources"
|
|
severity="Warning"
|
|
message="The resource `R.string.age_hint` appears to be unused"
|
|
category="Performance"
|
|
priority="3"
|
|
summary="Unused resources"
|
|
explanation="Unused resources make applications larger and slow down builds.


The unused resource check can ignore tests. If you want to include resources that are only referenced from tests, consider packaging them in a test source set instead.

You can include test sources in the unused resource check by setting the system property `lint.unused-resources.include-tests=true`, and to exclude them (usually for performance reasons), use `lint.unused-resources.exclude-tests=true`.
"
|
|
errorLine1=" <string name="age_hint">Idade</string>"
|
|
errorLine2=" ~~~~~~~~~~~~~~~">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/src/main/res/values/strings.xml"
|
|
line="16"
|
|
column="13"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="UnusedResources"
|
|
severity="Warning"
|
|
message="The resource `R.style.ShapeAppearanceOverlay_App_CornerSize50Percent` appears to be unused"
|
|
category="Performance"
|
|
priority="3"
|
|
summary="Unused resources"
|
|
explanation="Unused resources make applications larger and slow down builds.


The unused resource check can ignore tests. If you want to include resources that are only referenced from tests, consider packaging them in a test source set instead.

You can include test sources in the unused resource check by setting the system property `lint.unused-resources.include-tests=true`, and to exclude them (usually for performance reasons), use `lint.unused-resources.exclude-tests=true`.
"
|
|
errorLine1=" <style name="ShapeAppearanceOverlay.App.CornerSize50Percent" parent="">"
|
|
errorLine2=" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/src/main/res/values/themes.xml"
|
|
line="46"
|
|
column="12"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="IconLocation"
|
|
severity="Warning"
|
|
message="Found bitmap drawable `res/drawable/.!2449!ic_logo.png` in densityless folder"
|
|
category="Usability:Icons"
|
|
priority="5"
|
|
summary="Image defined in density-independent drawable folder"
|
|
explanation="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`."
|
|
url="https://developer.android.com/guide/practices/screens_support.html"
|
|
urls="https://developer.android.com/guide/practices/screens_support.html">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/src/main/res/drawable/.!2449!ic_logo.png"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="IconLocation"
|
|
severity="Warning"
|
|
message="Found bitmap drawable `res/drawable/ic_logo.png` in densityless folder"
|
|
category="Usability:Icons"
|
|
priority="5"
|
|
summary="Image defined in density-independent drawable folder"
|
|
explanation="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`."
|
|
url="https://developer.android.com/guide/practices/screens_support.html"
|
|
urls="https://developer.android.com/guide/practices/screens_support.html">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/src/main/res/drawable/ic_logo.png"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="IconLocation"
|
|
severity="Warning"
|
|
message="Found bitmap drawable `res/drawable/logo_app.png` in densityless folder"
|
|
category="Usability:Icons"
|
|
priority="5"
|
|
summary="Image defined in density-independent drawable folder"
|
|
explanation="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`."
|
|
url="https://developer.android.com/guide/practices/screens_support.html"
|
|
urls="https://developer.android.com/guide/practices/screens_support.html">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/src/main/res/drawable/logo_app.png"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="IconDuplicates"
|
|
severity="Warning"
|
|
message="The following unrelated icon files have identical contents: ic_launcher.png, ic_launcher_round.png"
|
|
category="Usability:Icons"
|
|
priority="3"
|
|
summary="Duplicated icons under different names"
|
|
explanation="If an icon is repeated under different names, you can consolidate and just use one of the icons and delete the others to make your application smaller. However, duplicated icons usually are not intentional and can sometimes point to icons that were accidentally overwritten or accidentally not updated.">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/src/main/res/mipmap-hdpi/ic_launcher_round.png"/>
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/src/main/res/mipmap-hdpi/ic_launcher.png"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="IconDuplicates"
|
|
severity="Warning"
|
|
message="The following unrelated icon files have identical contents: ic_launcher.png, ic_launcher_round.png"
|
|
category="Usability:Icons"
|
|
priority="3"
|
|
summary="Duplicated icons under different names"
|
|
explanation="If an icon is repeated under different names, you can consolidate and just use one of the icons and delete the others to make your application smaller. However, duplicated icons usually are not intentional and can sometimes point to icons that were accidentally overwritten or accidentally not updated.">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/src/main/res/mipmap-mdpi/ic_launcher_round.png"/>
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/src/main/res/mipmap-mdpi/ic_launcher.png"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="IconDuplicates"
|
|
severity="Warning"
|
|
message="The following unrelated icon files have identical contents: ic_launcher.png, ic_launcher_round.png"
|
|
category="Usability:Icons"
|
|
priority="3"
|
|
summary="Duplicated icons under different names"
|
|
explanation="If an icon is repeated under different names, you can consolidate and just use one of the icons and delete the others to make your application smaller. However, duplicated icons usually are not intentional and can sometimes point to icons that were accidentally overwritten or accidentally not updated.">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/src/main/res/mipmap-xhdpi/ic_launcher_round.png"/>
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/src/main/res/mipmap-xhdpi/ic_launcher.png"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="IconDuplicates"
|
|
severity="Warning"
|
|
message="The following unrelated icon files have identical contents: ic_launcher.png, ic_launcher_round.png"
|
|
category="Usability:Icons"
|
|
priority="3"
|
|
summary="Duplicated icons under different names"
|
|
explanation="If an icon is repeated under different names, you can consolidate and just use one of the icons and delete the others to make your application smaller. However, duplicated icons usually are not intentional and can sometimes point to icons that were accidentally overwritten or accidentally not updated.">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/src/main/res/mipmap-xxhdpi/ic_launcher_round.png"/>
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/src/main/res/mipmap-xxhdpi/ic_launcher.png"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="IconDuplicates"
|
|
severity="Warning"
|
|
message="The following unrelated icon files have identical contents: ic_launcher.png, ic_launcher_round.png"
|
|
category="Usability:Icons"
|
|
priority="3"
|
|
summary="Duplicated icons under different names"
|
|
explanation="If an icon is repeated under different names, you can consolidate and just use one of the icons and delete the others to make your application smaller. However, duplicated icons usually are not intentional and can sometimes point to icons that were accidentally overwritten or accidentally not updated.">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/src/main/res/mipmap-xxxhdpi/ic_launcher_round.png"/>
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/src/main/res/mipmap-xxxhdpi/ic_launcher.png"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="ContentDescription"
|
|
severity="Warning"
|
|
message="Missing `contentDescription` attribute on image"
|
|
category="Accessibility"
|
|
priority="3"
|
|
summary="Image without `contentDescription`"
|
|
explanation="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, set their descriptions to `@null`. If your app's minSdkVersion is 16 or higher, you can instead set these graphical elements' `android:importantForAccessibility` attributes to `no`.

Note that for text fields, you should not set both the `hint` and the `contentDescription` attributes since the hint will never be shown. Just set the `hint`."
|
|
url="https://developer.android.com/guide/topics/ui/accessibility/apps#special-cases"
|
|
urls="https://developer.android.com/guide/topics/ui/accessibility/apps#special-cases"
|
|
errorLine1=" <ImageButton"
|
|
errorLine2=" ~~~~~~~~~~~">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/src/main/res/layout/activity_editar_perfil.xml"
|
|
line="15"
|
|
column="10"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="ContentDescription"
|
|
severity="Warning"
|
|
message="Missing `contentDescription` attribute on image"
|
|
category="Accessibility"
|
|
priority="3"
|
|
summary="Image without `contentDescription`"
|
|
explanation="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, set their descriptions to `@null`. If your app's minSdkVersion is 16 or higher, you can instead set these graphical elements' `android:importantForAccessibility` attributes to `no`.

Note that for text fields, you should not set both the `hint` and the `contentDescription` attributes since the hint will never be shown. Just set the `hint`."
|
|
url="https://developer.android.com/guide/topics/ui/accessibility/apps#special-cases"
|
|
urls="https://developer.android.com/guide/topics/ui/accessibility/apps#special-cases"
|
|
errorLine1=" <ImageView"
|
|
errorLine2=" ~~~~~~~~~">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/src/main/res/layout/activity_forgot_password.xml"
|
|
line="10"
|
|
column="6"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="ContentDescription"
|
|
severity="Warning"
|
|
message="Missing `contentDescription` attribute on image"
|
|
category="Accessibility"
|
|
priority="3"
|
|
summary="Image without `contentDescription`"
|
|
explanation="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, set their descriptions to `@null`. If your app's minSdkVersion is 16 or higher, you can instead set these graphical elements' `android:importantForAccessibility` attributes to `no`.

Note that for text fields, you should not set both the `hint` and the `contentDescription` attributes since the hint will never be shown. Just set the `hint`."
|
|
url="https://developer.android.com/guide/topics/ui/accessibility/apps#special-cases"
|
|
urls="https://developer.android.com/guide/topics/ui/accessibility/apps#special-cases"
|
|
errorLine1=" <ImageButton"
|
|
errorLine2=" ~~~~~~~~~~~">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/src/main/res/layout/activity_main.xml"
|
|
line="189"
|
|
column="22"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="ContentDescription"
|
|
severity="Warning"
|
|
message="Missing `contentDescription` attribute on image"
|
|
category="Accessibility"
|
|
priority="3"
|
|
summary="Image without `contentDescription`"
|
|
explanation="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, set their descriptions to `@null`. If your app's minSdkVersion is 16 or higher, you can instead set these graphical elements' `android:importantForAccessibility` attributes to `no`.

Note that for text fields, you should not set both the `hint` and the `contentDescription` attributes since the hint will never be shown. Just set the `hint`."
|
|
url="https://developer.android.com/guide/topics/ui/accessibility/apps#special-cases"
|
|
urls="https://developer.android.com/guide/topics/ui/accessibility/apps#special-cases"
|
|
errorLine1=" <ImageButton"
|
|
errorLine2=" ~~~~~~~~~~~">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/src/main/res/layout/activity_main.xml"
|
|
line="225"
|
|
column="22"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="ContentDescription"
|
|
severity="Warning"
|
|
message="Missing `contentDescription` attribute on image"
|
|
category="Accessibility"
|
|
priority="3"
|
|
summary="Image without `contentDescription`"
|
|
explanation="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, set their descriptions to `@null`. If your app's minSdkVersion is 16 or higher, you can instead set these graphical elements' `android:importantForAccessibility` attributes to `no`.

Note that for text fields, you should not set both the `hint` and the `contentDescription` attributes since the hint will never be shown. Just set the `hint`."
|
|
url="https://developer.android.com/guide/topics/ui/accessibility/apps#special-cases"
|
|
urls="https://developer.android.com/guide/topics/ui/accessibility/apps#special-cases"
|
|
errorLine1=" <ImageButton"
|
|
errorLine2=" ~~~~~~~~~~~">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/src/main/res/layout/activity_main.xml"
|
|
line="234"
|
|
column="22"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="KeyboardInaccessibleWidget"
|
|
severity="Warning"
|
|
message="'clickable' attribute found, please also add 'focusable'"
|
|
category="Accessibility"
|
|
priority="3"
|
|
summary="Keyboard inaccessible widget"
|
|
explanation="A widget that is declared to be clickable but not declared to be focusable is not accessible via the keyboard. Please add the `focusable` attribute as well."
|
|
errorLine1=" android:clickable="true""
|
|
errorLine2=" ~~~~~~~~~~~~~~~~~~~~~~~~">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/src/main/res/layout/activity_editar_perfil.xml"
|
|
line="126"
|
|
column="21"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="KeyboardInaccessibleWidget"
|
|
severity="Warning"
|
|
message="'clickable' attribute found, please also add 'focusable'"
|
|
category="Accessibility"
|
|
priority="3"
|
|
summary="Keyboard inaccessible widget"
|
|
explanation="A widget that is declared to be clickable but not declared to be focusable is not accessible via the keyboard. Please add the `focusable` attribute as well."
|
|
errorLine1=" android:clickable="true""
|
|
errorLine2=" ~~~~~~~~~~~~~~~~~~~~~~~~">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/src/main/res/layout/activity_editar_perfil.xml"
|
|
line="143"
|
|
column="21"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="LabelFor"
|
|
severity="Warning"
|
|
message="Missing accessibility label: provide either a view with an `android:labelFor` that references this view or provide an `android:hint`"
|
|
category="Accessibility"
|
|
priority="2"
|
|
summary="Missing accessibility label"
|
|
explanation="Editable text fields should provide an `android:hint` or, provided your `minSdkVersion` is at least 17, they may be referenced by a view with a `android:labelFor` attribute.

When using `android:labelFor`, be sure to provide an `android:text` or an `android:contentDescription`.

If your view is labeled but by a label in a different layout which includes this one, just suppress this warning from lint."
|
|
errorLine1=" <AutoCompleteTextView"
|
|
errorLine2=" ~~~~~~~~~~~~~~~~~~~~">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/src/main/res/layout/activity_editar_perfil.xml"
|
|
line="100"
|
|
column="14"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="LabelFor"
|
|
severity="Warning"
|
|
message="Missing accessibility label: provide either a view with an `android:labelFor` that references this view or provide an `android:hint`"
|
|
category="Accessibility"
|
|
priority="2"
|
|
summary="Missing accessibility label"
|
|
explanation="Editable text fields should provide an `android:hint` or, provided your `minSdkVersion` is at least 17, they may be referenced by a view with a `android:labelFor` attribute.

When using `android:labelFor`, be sure to provide an `android:text` or an `android:contentDescription`.

If your view is labeled but by a label in a different layout which includes this one, just suppress this warning from lint."
|
|
errorLine1=" <AutoCompleteTextView"
|
|
errorLine2=" ~~~~~~~~~~~~~~~~~~~~">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/src/main/res/layout/activity_register.xml"
|
|
line="84"
|
|
column="22"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="SetTextI18n"
|
|
severity="Warning"
|
|
message="String literal in `setText` can not be translated. Use Android resources instead."
|
|
category="Internationalization"
|
|
priority="6"
|
|
summary="TextView Internationalization"
|
|
explanation="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."
|
|
url="https://developer.android.com/guide/topics/resources/localization.html"
|
|
urls="https://developer.android.com/guide/topics/resources/localization.html"
|
|
errorLine1=" textPacienteNome.setText("A carregar nome...");"
|
|
errorLine2=" ~~~~~~~~~~~~~~~~~~~~">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/src/main/java/com/example/medcuida/pro/ui/adapters/ConsultaAdapter.java"
|
|
line="90"
|
|
column="42"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="SetTextI18n"
|
|
severity="Warning"
|
|
message="String literal in `setText` can not be translated. Use Android resources instead."
|
|
category="Internationalization"
|
|
priority="6"
|
|
summary="TextView Internationalization"
|
|
explanation="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."
|
|
url="https://developer.android.com/guide/topics/resources/localization.html"
|
|
urls="https://developer.android.com/guide/topics/resources/localization.html"
|
|
errorLine1=" textPacienteNome.setText("Paciente s/ Nome");"
|
|
errorLine2=" ~~~~~~~~~~~~~~~~~~">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/src/main/java/com/example/medcuida/pro/ui/adapters/ConsultaAdapter.java"
|
|
line="102"
|
|
column="58"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="SetTextI18n"
|
|
severity="Warning"
|
|
message="String literal in `setText` can not be translated. Use Android resources instead."
|
|
category="Internationalization"
|
|
priority="6"
|
|
summary="TextView Internationalization"
|
|
explanation="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."
|
|
url="https://developer.android.com/guide/topics/resources/localization.html"
|
|
urls="https://developer.android.com/guide/topics/resources/localization.html"
|
|
errorLine1=" textPacienteNome.setText("Paciente Apagado");"
|
|
errorLine2=" ~~~~~~~~~~~~~~~~~~">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/src/main/java/com/example/medcuida/pro/ui/adapters/ConsultaAdapter.java"
|
|
line="105"
|
|
column="54"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="SetTextI18n"
|
|
severity="Warning"
|
|
message="Do not concatenate text displayed with `setText`. Use resource string with placeholders."
|
|
category="Internationalization"
|
|
priority="6"
|
|
summary="TextView Internationalization"
|
|
explanation="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."
|
|
url="https://developer.android.com/guide/topics/resources/localization.html"
|
|
urls="https://developer.android.com/guide/topics/resources/localization.html"
|
|
errorLine1=" tvNome.setText("Nome: " + (nome != null ? nome : "N/D"));"
|
|
errorLine2=" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/src/main/java/com/example/medcuida/pro/DetalhePacienteActivity.java"
|
|
line="76"
|
|
column="44"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="SetTextI18n"
|
|
severity="Warning"
|
|
message="String literal in `setText` can not be translated. Use Android resources instead."
|
|
category="Internationalization"
|
|
priority="6"
|
|
summary="TextView Internationalization"
|
|
explanation="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."
|
|
url="https://developer.android.com/guide/topics/resources/localization.html"
|
|
urls="https://developer.android.com/guide/topics/resources/localization.html"
|
|
errorLine1=" tvNome.setText("Nome: " + (nome != null ? nome : "N/D"));"
|
|
errorLine2=" ~~~~~~~~">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/src/main/java/com/example/medcuida/pro/DetalhePacienteActivity.java"
|
|
line="76"
|
|
column="44"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="SetTextI18n"
|
|
severity="Warning"
|
|
message="Do not concatenate text displayed with `setText`. Use resource string with placeholders."
|
|
category="Internationalization"
|
|
priority="6"
|
|
summary="TextView Internationalization"
|
|
explanation="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."
|
|
url="https://developer.android.com/guide/topics/resources/localization.html"
|
|
urls="https://developer.android.com/guide/topics/resources/localization.html"
|
|
errorLine1=" tvIdade.setText("Idade: " + (idade != null ? idade : "N/D"));"
|
|
errorLine2=" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/src/main/java/com/example/medcuida/pro/DetalhePacienteActivity.java"
|
|
line="77"
|
|
column="45"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="SetTextI18n"
|
|
severity="Warning"
|
|
message="String literal in `setText` can not be translated. Use Android resources instead."
|
|
category="Internationalization"
|
|
priority="6"
|
|
summary="TextView Internationalization"
|
|
explanation="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."
|
|
url="https://developer.android.com/guide/topics/resources/localization.html"
|
|
urls="https://developer.android.com/guide/topics/resources/localization.html"
|
|
errorLine1=" tvIdade.setText("Idade: " + (idade != null ? idade : "N/D"));"
|
|
errorLine2=" ~~~~~~~~~">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/src/main/java/com/example/medcuida/pro/DetalhePacienteActivity.java"
|
|
line="77"
|
|
column="45"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="SetTextI18n"
|
|
severity="Warning"
|
|
message="Do not concatenate text displayed with `setText`. Use resource string with placeholders."
|
|
category="Internationalization"
|
|
priority="6"
|
|
summary="TextView Internationalization"
|
|
explanation="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."
|
|
url="https://developer.android.com/guide/topics/resources/localization.html"
|
|
urls="https://developer.android.com/guide/topics/resources/localization.html"
|
|
errorLine1=" tvNumeroUtente.setText("Nº Utente: " + (numUtente != null ? numUtente : "N/D"));"
|
|
errorLine2=" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/src/main/java/com/example/medcuida/pro/DetalhePacienteActivity.java"
|
|
line="78"
|
|
column="52"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="SetTextI18n"
|
|
severity="Warning"
|
|
message="String literal in `setText` can not be translated. Use Android resources instead."
|
|
category="Internationalization"
|
|
priority="6"
|
|
summary="TextView Internationalization"
|
|
explanation="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."
|
|
url="https://developer.android.com/guide/topics/resources/localization.html"
|
|
urls="https://developer.android.com/guide/topics/resources/localization.html"
|
|
errorLine1=" tvNumeroUtente.setText("Nº Utente: " + (numUtente != null ? numUtente : "N/D"));"
|
|
errorLine2=" ~~~~~~~~~~~~~">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/src/main/java/com/example/medcuida/pro/DetalhePacienteActivity.java"
|
|
line="78"
|
|
column="52"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="SetTextI18n"
|
|
severity="Warning"
|
|
message="Do not concatenate text displayed with `setText`. Use resource string with placeholders."
|
|
category="Internationalization"
|
|
priority="6"
|
|
summary="TextView Internationalization"
|
|
explanation="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."
|
|
url="https://developer.android.com/guide/topics/resources/localization.html"
|
|
urls="https://developer.android.com/guide/topics/resources/localization.html"
|
|
errorLine1=" tvSexo.setText("Sexo: " + (sexo != null ? sexo : "N/D"));"
|
|
errorLine2=" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/src/main/java/com/example/medcuida/pro/DetalhePacienteActivity.java"
|
|
line="79"
|
|
column="44"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="SetTextI18n"
|
|
severity="Warning"
|
|
message="String literal in `setText` can not be translated. Use Android resources instead."
|
|
category="Internationalization"
|
|
priority="6"
|
|
summary="TextView Internationalization"
|
|
explanation="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."
|
|
url="https://developer.android.com/guide/topics/resources/localization.html"
|
|
urls="https://developer.android.com/guide/topics/resources/localization.html"
|
|
errorLine1=" tvSexo.setText("Sexo: " + (sexo != null ? sexo : "N/D"));"
|
|
errorLine2=" ~~~~~~~~">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/src/main/java/com/example/medcuida/pro/DetalhePacienteActivity.java"
|
|
line="79"
|
|
column="44"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="SetTextI18n"
|
|
severity="Warning"
|
|
message="Do not concatenate text displayed with `setText`. Use resource string with placeholders."
|
|
category="Internationalization"
|
|
priority="6"
|
|
summary="TextView Internationalization"
|
|
explanation="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."
|
|
url="https://developer.android.com/guide/topics/resources/localization.html"
|
|
urls="https://developer.android.com/guide/topics/resources/localization.html"
|
|
errorLine1=" tvEmail.setText("Email: " + (email != null ? email : "N/D"));"
|
|
errorLine2=" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/src/main/java/com/example/medcuida/pro/DetalhePacienteActivity.java"
|
|
line="80"
|
|
column="45"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="SetTextI18n"
|
|
severity="Warning"
|
|
message="String literal in `setText` can not be translated. Use Android resources instead."
|
|
category="Internationalization"
|
|
priority="6"
|
|
summary="TextView Internationalization"
|
|
explanation="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."
|
|
url="https://developer.android.com/guide/topics/resources/localization.html"
|
|
urls="https://developer.android.com/guide/topics/resources/localization.html"
|
|
errorLine1=" tvEmail.setText("Email: " + (email != null ? email : "N/D"));"
|
|
errorLine2=" ~~~~~~~~~">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/src/main/java/com/example/medcuida/pro/DetalhePacienteActivity.java"
|
|
line="80"
|
|
column="45"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="SetTextI18n"
|
|
severity="Warning"
|
|
message="String literal in `setText` can not be translated. Use Android resources instead."
|
|
category="Internationalization"
|
|
priority="6"
|
|
summary="TextView Internationalization"
|
|
explanation="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."
|
|
url="https://developer.android.com/guide/topics/resources/localization.html"
|
|
urls="https://developer.android.com/guide/topics/resources/localization.html"
|
|
errorLine1=" loginButton.setText("A entrar...");"
|
|
errorLine2=" ~~~~~~~~~~~~~">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/src/main/java/com/example/medcuida/pro/ui/auth/LoginActivity.java"
|
|
line="95"
|
|
column="29"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="SetTextI18n"
|
|
severity="Warning"
|
|
message="String literal in `setText` can not be translated. Use Android resources instead."
|
|
category="Internationalization"
|
|
priority="6"
|
|
summary="TextView Internationalization"
|
|
explanation="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."
|
|
url="https://developer.android.com/guide/topics/resources/localization.html"
|
|
urls="https://developer.android.com/guide/topics/resources/localization.html"
|
|
errorLine1=" loginButton.setText("Entrar");"
|
|
errorLine2=" ~~~~~~~~">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/src/main/java/com/example/medcuida/pro/ui/auth/LoginActivity.java"
|
|
line="108"
|
|
column="45"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="SetTextI18n"
|
|
severity="Warning"
|
|
message="String literal in `setText` can not be translated. Use Android resources instead."
|
|
category="Internationalization"
|
|
priority="6"
|
|
summary="TextView Internationalization"
|
|
explanation="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."
|
|
url="https://developer.android.com/guide/topics/resources/localization.html"
|
|
urls="https://developer.android.com/guide/topics/resources/localization.html"
|
|
errorLine1=" loginButton.setText("Entrar");"
|
|
errorLine2=" ~~~~~~~~">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/src/main/java/com/example/medcuida/pro/ui/auth/LoginActivity.java"
|
|
line="156"
|
|
column="61"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="SetTextI18n"
|
|
severity="Warning"
|
|
message="Do not concatenate text displayed with `setText`. Use resource string with placeholders."
|
|
category="Internationalization"
|
|
priority="6"
|
|
summary="TextView Internationalization"
|
|
explanation="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."
|
|
url="https://developer.android.com/guide/topics/resources/localization.html"
|
|
urls="https://developer.android.com/guide/topics/resources/localization.html"
|
|
errorLine1=" tvGreetingMain.setText("Olá, " + firstWord);"
|
|
errorLine2=" ~~~~~~~~~~~~~~~~~~~">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/src/main/java/com/example/medcuida/pro/MainActivity.java"
|
|
line="117"
|
|
column="40"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="SetTextI18n"
|
|
severity="Warning"
|
|
message="String literal in `setText` can not be translated. Use Android resources instead."
|
|
category="Internationalization"
|
|
priority="6"
|
|
summary="TextView Internationalization"
|
|
explanation="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."
|
|
url="https://developer.android.com/guide/topics/resources/localization.html"
|
|
urls="https://developer.android.com/guide/topics/resources/localization.html"
|
|
errorLine1=" tvGreetingMain.setText("Olá, " + firstWord);"
|
|
errorLine2=" ~~~~~~~">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/src/main/java/com/example/medcuida/pro/MainActivity.java"
|
|
line="117"
|
|
column="40"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="SetTextI18n"
|
|
severity="Warning"
|
|
message="String literal in `setText` can not be translated. Use Android resources instead."
|
|
category="Internationalization"
|
|
priority="6"
|
|
summary="TextView Internationalization"
|
|
explanation="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."
|
|
url="https://developer.android.com/guide/topics/resources/localization.html"
|
|
urls="https://developer.android.com/guide/topics/resources/localization.html"
|
|
errorLine1=" textAgendaVazia.setText("Não existem consultas agendadas para este dia.");"
|
|
errorLine2=" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/src/main/java/com/example/medcuida/pro/MainActivity.java"
|
|
line="467"
|
|
column="49"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="SetTextI18n"
|
|
severity="Warning"
|
|
message="Do not concatenate text displayed with `setText`. Use resource string with placeholders."
|
|
category="Internationalization"
|
|
priority="6"
|
|
summary="TextView Internationalization"
|
|
explanation="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."
|
|
url="https://developer.android.com/guide/topics/resources/localization.html"
|
|
urls="https://developer.android.com/guide/topics/resources/localization.html"
|
|
errorLine1=" tvGreetingMain.setText("Olá, " + firstWord);"
|
|
errorLine2=" ~~~~~~~~~~~~~~~~~~~">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/src/main/java/com/example/medcuida/pro/MainActivity.java"
|
|
line="629"
|
|
column="36"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="SetTextI18n"
|
|
severity="Warning"
|
|
message="String literal in `setText` can not be translated. Use Android resources instead."
|
|
category="Internationalization"
|
|
priority="6"
|
|
summary="TextView Internationalization"
|
|
explanation="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."
|
|
url="https://developer.android.com/guide/topics/resources/localization.html"
|
|
urls="https://developer.android.com/guide/topics/resources/localization.html"
|
|
errorLine1=" tvGreetingMain.setText("Olá, " + firstWord);"
|
|
errorLine2=" ~~~~~~~">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/src/main/java/com/example/medcuida/pro/MainActivity.java"
|
|
line="629"
|
|
column="36"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="SetTextI18n"
|
|
severity="Warning"
|
|
message="Do not concatenate text displayed with `setText`. Use resource string with placeholders."
|
|
category="Internationalization"
|
|
priority="6"
|
|
summary="TextView Internationalization"
|
|
explanation="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."
|
|
url="https://developer.android.com/guide/topics/resources/localization.html"
|
|
urls="https://developer.android.com/guide/topics/resources/localization.html"
|
|
errorLine1=" "Especialidade: " + (doc.getString("especialidade") != null ? doc.getString("especialidade") : "--"));"
|
|
errorLine2=" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/src/main/java/com/example/medcuida/pro/MainActivity.java"
|
|
line="633"
|
|
column="17"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="SetTextI18n"
|
|
severity="Warning"
|
|
message="String literal in `setText` can not be translated. Use Android resources instead."
|
|
category="Internationalization"
|
|
priority="6"
|
|
summary="TextView Internationalization"
|
|
explanation="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."
|
|
url="https://developer.android.com/guide/topics/resources/localization.html"
|
|
urls="https://developer.android.com/guide/topics/resources/localization.html"
|
|
errorLine1=" "Especialidade: " + (doc.getString("especialidade") != null ? doc.getString("especialidade") : "--"));"
|
|
errorLine2=" ~~~~~~~~~~~~~~~~~">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/src/main/java/com/example/medcuida/pro/MainActivity.java"
|
|
line="633"
|
|
column="17"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="SetTextI18n"
|
|
severity="Warning"
|
|
message="Do not concatenate text displayed with `setText`. Use resource string with placeholders."
|
|
category="Internationalization"
|
|
priority="6"
|
|
summary="TextView Internationalization"
|
|
explanation="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."
|
|
url="https://developer.android.com/guide/topics/resources/localization.html"
|
|
urls="https://developer.android.com/guide/topics/resources/localization.html"
|
|
errorLine1=" tvCedula.setText("Género: " + (sexo != null && !sexo.isEmpty() ? sexo : "--"));"
|
|
errorLine2=" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/src/main/java/com/example/medcuida/pro/MainActivity.java"
|
|
line="638"
|
|
column="26"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="SetTextI18n"
|
|
severity="Warning"
|
|
message="String literal in `setText` can not be translated. Use Android resources instead."
|
|
category="Internationalization"
|
|
priority="6"
|
|
summary="TextView Internationalization"
|
|
explanation="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."
|
|
url="https://developer.android.com/guide/topics/resources/localization.html"
|
|
urls="https://developer.android.com/guide/topics/resources/localization.html"
|
|
errorLine1=" tvCedula.setText("Género: " + (sexo != null && !sexo.isEmpty() ? sexo : "--"));"
|
|
errorLine2=" ~~~~~~~~~~">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/src/main/java/com/example/medcuida/pro/MainActivity.java"
|
|
line="638"
|
|
column="26"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="SetTextI18n"
|
|
severity="Warning"
|
|
message="Do not concatenate text displayed with `setText`. Use resource string with placeholders."
|
|
category="Internationalization"
|
|
priority="6"
|
|
summary="TextView Internationalization"
|
|
explanation="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."
|
|
url="https://developer.android.com/guide/topics/resources/localization.html"
|
|
urls="https://developer.android.com/guide/topics/resources/localization.html"
|
|
errorLine1=" tvHorario.setText("Horário: " + (horario != null && !horario.isEmpty() ? horario : "--"));"
|
|
errorLine2=" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/src/main/java/com/example/medcuida/pro/MainActivity.java"
|
|
line="639"
|
|
column="27"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="SetTextI18n"
|
|
severity="Warning"
|
|
message="String literal in `setText` can not be translated. Use Android resources instead."
|
|
category="Internationalization"
|
|
priority="6"
|
|
summary="TextView Internationalization"
|
|
explanation="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."
|
|
url="https://developer.android.com/guide/topics/resources/localization.html"
|
|
urls="https://developer.android.com/guide/topics/resources/localization.html"
|
|
errorLine1=" tvHorario.setText("Horário: " + (horario != null && !horario.isEmpty() ? horario : "--"));"
|
|
errorLine2=" ~~~~~~~~~~~">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/src/main/java/com/example/medcuida/pro/MainActivity.java"
|
|
line="639"
|
|
column="27"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="HardcodedText"
|
|
severity="Warning"
|
|
message="Hardcoded string "Sair", should use `@string` resource"
|
|
category="Internationalization"
|
|
priority="5"
|
|
summary="Hardcoded text"
|
|
explanation="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."
|
|
errorLine1=" android:contentDescription="Sair""
|
|
errorLine2=" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/src/main/res/layout/activity_detalhe_paciente.xml"
|
|
line="22"
|
|
column="9"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="HardcodedText"
|
|
severity="Warning"
|
|
message="Hardcoded string "Informação Pessoal", should use `@string` resource"
|
|
category="Internationalization"
|
|
priority="5"
|
|
summary="Hardcoded text"
|
|
explanation="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."
|
|
errorLine1=" android:text="Informação Pessoal""
|
|
errorLine2=" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/src/main/res/layout/activity_detalhe_paciente.xml"
|
|
line="57"
|
|
column="25"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="HardcodedText"
|
|
severity="Warning"
|
|
message="Hardcoded string "Nome: A carregar...", should use `@string` resource"
|
|
category="Internationalization"
|
|
priority="5"
|
|
summary="Hardcoded text"
|
|
explanation="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."
|
|
errorLine1=" android:text="Nome: A carregar...""
|
|
errorLine2=" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/src/main/res/layout/activity_detalhe_paciente.xml"
|
|
line="67"
|
|
column="25"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="HardcodedText"
|
|
severity="Warning"
|
|
message="Hardcoded string "Idade: A carregar...", should use `@string` resource"
|
|
category="Internationalization"
|
|
priority="5"
|
|
summary="Hardcoded text"
|
|
explanation="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."
|
|
errorLine1=" android:text="Idade: A carregar...""
|
|
errorLine2=" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/src/main/res/layout/activity_detalhe_paciente.xml"
|
|
line="75"
|
|
column="25"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="HardcodedText"
|
|
severity="Warning"
|
|
message="Hardcoded string "Nº Utente: A carregar...", should use `@string` resource"
|
|
category="Internationalization"
|
|
priority="5"
|
|
summary="Hardcoded text"
|
|
explanation="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."
|
|
errorLine1=" android:text="Nº Utente: A carregar...""
|
|
errorLine2=" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/src/main/res/layout/activity_detalhe_paciente.xml"
|
|
line="83"
|
|
column="25"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="HardcodedText"
|
|
severity="Warning"
|
|
message="Hardcoded string "Sexo: A carregar...", should use `@string` resource"
|
|
category="Internationalization"
|
|
priority="5"
|
|
summary="Hardcoded text"
|
|
explanation="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."
|
|
errorLine1=" android:text="Sexo: A carregar...""
|
|
errorLine2=" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/src/main/res/layout/activity_detalhe_paciente.xml"
|
|
line="91"
|
|
column="25"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="HardcodedText"
|
|
severity="Warning"
|
|
message="Hardcoded string "Email: A carregar...", should use `@string` resource"
|
|
category="Internationalization"
|
|
priority="5"
|
|
summary="Hardcoded text"
|
|
explanation="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."
|
|
errorLine1=" android:text="Email: A carregar...""
|
|
errorLine2=" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/src/main/res/layout/activity_detalhe_paciente.xml"
|
|
line="99"
|
|
column="25"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="HardcodedText"
|
|
severity="Warning"
|
|
message="Hardcoded string "Medicação Ativa", should use `@string` resource"
|
|
category="Internationalization"
|
|
priority="5"
|
|
summary="Hardcoded text"
|
|
explanation="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."
|
|
errorLine1=" android:text="Medicação Ativa""
|
|
errorLine2=" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/src/main/res/layout/activity_detalhe_paciente.xml"
|
|
line="125"
|
|
column="25"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="HardcodedText"
|
|
severity="Warning"
|
|
message="Hardcoded string "A carregar medicação...", should use `@string` resource"
|
|
category="Internationalization"
|
|
priority="5"
|
|
summary="Hardcoded text"
|
|
explanation="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."
|
|
errorLine1=" android:text="A carregar medicação...""
|
|
errorLine2=" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/src/main/res/layout/activity_detalhe_paciente.xml"
|
|
line="135"
|
|
column="25"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="HardcodedText"
|
|
severity="Warning"
|
|
message="Hardcoded string "Ações", should use `@string` resource"
|
|
category="Internationalization"
|
|
priority="5"
|
|
summary="Hardcoded text"
|
|
explanation="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."
|
|
errorLine1=" android:text="Ações""
|
|
errorLine2=" ~~~~~~~~~~~~~~~~~~~~">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/src/main/res/layout/activity_detalhe_paciente.xml"
|
|
line="162"
|
|
column="25"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="HardcodedText"
|
|
severity="Warning"
|
|
message="Hardcoded string "Enviar para App do Paciente", should use `@string` resource"
|
|
category="Internationalization"
|
|
priority="5"
|
|
summary="Hardcoded text"
|
|
explanation="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."
|
|
errorLine1=" android:text="Enviar para App do Paciente""
|
|
errorLine2=" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/src/main/res/layout/activity_detalhe_paciente.xml"
|
|
line="172"
|
|
column="25"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="HardcodedText"
|
|
severity="Warning"
|
|
message="Hardcoded string "Partilhar Relatório", should use `@string` resource"
|
|
category="Internationalization"
|
|
priority="5"
|
|
summary="Hardcoded text"
|
|
explanation="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."
|
|
errorLine1=" android:text="Partilhar Relatório""
|
|
errorLine2=" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/src/main/res/layout/activity_detalhe_paciente.xml"
|
|
line="181"
|
|
column="25"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="HardcodedText"
|
|
severity="Warning"
|
|
message="Hardcoded string "Editar Dados Pessoais", should use `@string` resource"
|
|
category="Internationalization"
|
|
priority="5"
|
|
summary="Hardcoded text"
|
|
explanation="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."
|
|
errorLine1=" android:text="Editar Dados Pessoais""
|
|
errorLine2=" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/src/main/res/layout/activity_editar_perfil.xml"
|
|
line="26"
|
|
column="13"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="HardcodedText"
|
|
severity="Warning"
|
|
message="Hardcoded string "Editar foto", should use `@string` resource"
|
|
category="Internationalization"
|
|
priority="5"
|
|
summary="Hardcoded text"
|
|
explanation="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."
|
|
errorLine1=" android:contentDescription="Editar foto"/>"
|
|
errorLine2=" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/src/main/res/layout/activity_editar_perfil.xml"
|
|
line="58"
|
|
column="17"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="HardcodedText"
|
|
severity="Warning"
|
|
message="Hardcoded string "Nome", should use `@string` resource"
|
|
category="Internationalization"
|
|
priority="5"
|
|
summary="Hardcoded text"
|
|
explanation="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."
|
|
errorLine1=" android:hint="Nome""
|
|
errorLine2=" ~~~~~~~~~~~~~~~~~~~">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/src/main/res/layout/activity_editar_perfil.xml"
|
|
line="71"
|
|
column="17"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="HardcodedText"
|
|
severity="Warning"
|
|
message="Hardcoded string "Especialidade", should use `@string` resource"
|
|
category="Internationalization"
|
|
priority="5"
|
|
summary="Hardcoded text"
|
|
explanation="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."
|
|
errorLine1=" android:hint="Especialidade""
|
|
errorLine2=" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/src/main/res/layout/activity_editar_perfil.xml"
|
|
line="87"
|
|
column="17"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="HardcodedText"
|
|
severity="Warning"
|
|
message="Hardcoded string "Sexo", should use `@string` resource"
|
|
category="Internationalization"
|
|
priority="5"
|
|
summary="Hardcoded text"
|
|
explanation="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."
|
|
errorLine1=" android:hint="Sexo">"
|
|
errorLine2=" ~~~~~~~~~~~~~~~~~~~">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/src/main/res/layout/activity_editar_perfil.xml"
|
|
line="98"
|
|
column="13"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="HardcodedText"
|
|
severity="Warning"
|
|
message="Hardcoded string "Início", should use `@string` resource"
|
|
category="Internationalization"
|
|
priority="5"
|
|
summary="Hardcoded text"
|
|
explanation="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."
|
|
errorLine1=" android:hint="Início""
|
|
errorLine2=" ~~~~~~~~~~~~~~~~~~~~~">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/src/main/res/layout/activity_editar_perfil.xml"
|
|
line="124"
|
|
column="21"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="HardcodedText"
|
|
severity="Warning"
|
|
message="Hardcoded string "Fim", should use `@string` resource"
|
|
category="Internationalization"
|
|
priority="5"
|
|
summary="Hardcoded text"
|
|
explanation="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."
|
|
errorLine1=" android:hint="Fim""
|
|
errorLine2=" ~~~~~~~~~~~~~~~~~~">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/src/main/res/layout/activity_editar_perfil.xml"
|
|
line="141"
|
|
column="21"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="HardcodedText"
|
|
severity="Warning"
|
|
message="Hardcoded string "Email (Não editável)", should use `@string` resource"
|
|
category="Internationalization"
|
|
priority="5"
|
|
summary="Hardcoded text"
|
|
explanation="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."
|
|
errorLine1=" android:hint="Email (Não editável)""
|
|
errorLine2=" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/src/main/res/layout/activity_editar_perfil.xml"
|
|
line="159"
|
|
column="17"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="HardcodedText"
|
|
severity="Warning"
|
|
message="Hardcoded string "GUARDAR ALTERAÇÕES", should use `@string` resource"
|
|
category="Internationalization"
|
|
priority="5"
|
|
summary="Hardcoded text"
|
|
explanation="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."
|
|
errorLine1=" android:text="GUARDAR ALTERAÇÕES""
|
|
errorLine2=" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/src/main/res/layout/activity_editar_perfil.xml"
|
|
line="167"
|
|
column="13"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="HardcodedText"
|
|
severity="Warning"
|
|
message="Hardcoded string "Insira o seu email para recuperar a palavra-passe.", should use `@string` resource"
|
|
category="Internationalization"
|
|
priority="5"
|
|
summary="Hardcoded text"
|
|
explanation="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."
|
|
errorLine1=" android:text="Insira o seu email para recuperar a palavra-passe.""
|
|
errorLine2=" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/src/main/res/layout/activity_forgot_password.xml"
|
|
line="29"
|
|
column="9"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="HardcodedText"
|
|
severity="Warning"
|
|
message="Hardcoded string "Recuperar Palavra-passe", should use `@string` resource"
|
|
category="Internationalization"
|
|
priority="5"
|
|
summary="Hardcoded text"
|
|
explanation="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."
|
|
errorLine1=" android:text="Recuperar Palavra-passe""
|
|
errorLine2=" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/src/main/res/layout/activity_forgot_password.xml"
|
|
line="55"
|
|
column="9"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="HardcodedText"
|
|
severity="Warning"
|
|
message="Hardcoded string "Voltar ao Login", should use `@string` resource"
|
|
category="Internationalization"
|
|
priority="5"
|
|
summary="Hardcoded text"
|
|
explanation="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."
|
|
errorLine1=" android:text="Voltar ao Login""
|
|
errorLine2=" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/src/main/res/layout/activity_forgot_password.xml"
|
|
line="63"
|
|
column="9"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="HardcodedText"
|
|
severity="Warning"
|
|
message="Hardcoded string "Lembrar-me", should use `@string` resource"
|
|
category="Internationalization"
|
|
priority="5"
|
|
summary="Hardcoded text"
|
|
explanation="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."
|
|
errorLine1=" android:text="Lembrar-me""
|
|
errorLine2=" ~~~~~~~~~~~~~~~~~~~~~~~~~">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/src/main/res/layout/activity_login.xml"
|
|
line="86"
|
|
column="21"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="HardcodedText"
|
|
severity="Warning"
|
|
message="Hardcoded string "Olá", should use `@string` resource"
|
|
category="Internationalization"
|
|
priority="5"
|
|
summary="Hardcoded text"
|
|
explanation="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."
|
|
errorLine1=" android:text="Olá""
|
|
errorLine2=" ~~~~~~~~~~~~~~~~~~">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/src/main/res/layout/activity_main.xml"
|
|
line="24"
|
|
column="13"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="HardcodedText"
|
|
severity="Warning"
|
|
message="Hardcoded string "Não tens consultas agendadas para este dia.", should use `@string` resource"
|
|
category="Internationalization"
|
|
priority="5"
|
|
summary="Hardcoded text"
|
|
explanation="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."
|
|
errorLine1=" android:text="Não tens consultas agendadas para este dia.""
|
|
errorLine2=" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/src/main/res/layout/activity_main.xml"
|
|
line="78"
|
|
column="21"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="HardcodedText"
|
|
severity="Warning"
|
|
message="Hardcoded string "Nomes dos Pacientes", should use `@string` resource"
|
|
category="Internationalization"
|
|
priority="5"
|
|
summary="Hardcoded text"
|
|
explanation="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."
|
|
errorLine1=" android:text="Nomes dos Pacientes""
|
|
errorLine2=" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/src/main/res/layout/activity_main.xml"
|
|
line="99"
|
|
column="17"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="HardcodedText"
|
|
severity="Warning"
|
|
message="Hardcoded string "Pesquisar por nome...", should use `@string` resource"
|
|
category="Internationalization"
|
|
priority="5"
|
|
summary="Hardcoded text"
|
|
explanation="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."
|
|
errorLine1=" android:hint="Pesquisar por nome...""
|
|
errorLine2=" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/src/main/res/layout/activity_main.xml"
|
|
line="129"
|
|
column="21"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="HardcodedText"
|
|
severity="Warning"
|
|
message="Hardcoded string "Nenhuma consulta marcada.", should use `@string` resource"
|
|
category="Internationalization"
|
|
priority="5"
|
|
summary="Hardcoded text"
|
|
explanation="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."
|
|
errorLine1=" android:text="Nenhuma consulta marcada.""
|
|
errorLine2=" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/src/main/res/layout/activity_main.xml"
|
|
line="139"
|
|
column="17"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="HardcodedText"
|
|
severity="Warning"
|
|
message="Hardcoded string "Histórico de Consultas", should use `@string` resource"
|
|
category="Internationalization"
|
|
priority="5"
|
|
summary="Hardcoded text"
|
|
explanation="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."
|
|
errorLine1=" android:text="Histórico de Consultas""
|
|
errorLine2=" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/src/main/res/layout/activity_main.xml"
|
|
line="166"
|
|
column="17"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="HardcodedText"
|
|
severity="Warning"
|
|
message="Hardcoded string "Selecionar Dia", should use `@string` resource"
|
|
category="Internationalization"
|
|
priority="5"
|
|
summary="Hardcoded text"
|
|
explanation="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."
|
|
errorLine1=" android:text="Selecionar Dia""
|
|
errorLine2=" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/src/main/res/layout/activity_main.xml"
|
|
line="211"
|
|
column="29"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="HardcodedText"
|
|
severity="Warning"
|
|
message="Hardcoded string "Data Selecionada", should use `@string` resource"
|
|
category="Internationalization"
|
|
priority="5"
|
|
summary="Hardcoded text"
|
|
explanation="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."
|
|
errorLine1=" android:text="Data Selecionada""
|
|
errorLine2=" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/src/main/res/layout/activity_main.xml"
|
|
line="220"
|
|
column="29"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="HardcodedText"
|
|
severity="Warning"
|
|
message="Hardcoded string "Nenhuma consulta encontrada para este dia.", should use `@string` resource"
|
|
category="Internationalization"
|
|
priority="5"
|
|
summary="Hardcoded text"
|
|
explanation="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."
|
|
errorLine1=" android:text="Nenhuma consulta encontrada para este dia.""
|
|
errorLine2=" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/src/main/res/layout/activity_main.xml"
|
|
line="249"
|
|
column="17"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="HardcodedText"
|
|
severity="Warning"
|
|
message="Hardcoded string "Nome do Utilizador", should use `@string` resource"
|
|
category="Internationalization"
|
|
priority="5"
|
|
summary="Hardcoded text"
|
|
explanation="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."
|
|
errorLine1=" android:text="Nome do Utilizador""
|
|
errorLine2=" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/src/main/res/layout/activity_main.xml"
|
|
line="309"
|
|
column="25"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="HardcodedText"
|
|
severity="Warning"
|
|
message="Hardcoded string "email@exemplo.com", should use `@string` resource"
|
|
category="Internationalization"
|
|
priority="5"
|
|
summary="Hardcoded text"
|
|
explanation="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."
|
|
errorLine1=" android:text="email@exemplo.com""
|
|
errorLine2=" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/src/main/res/layout/activity_main.xml"
|
|
line="319"
|
|
column="25"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="HardcodedText"
|
|
severity="Warning"
|
|
message="Hardcoded string "Especialidade: --", should use `@string` resource"
|
|
category="Internationalization"
|
|
priority="5"
|
|
summary="Hardcoded text"
|
|
explanation="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."
|
|
errorLine1=" android:text="Especialidade: --""
|
|
errorLine2=" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/src/main/res/layout/activity_main.xml"
|
|
line="335"
|
|
column="25"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="HardcodedText"
|
|
severity="Warning"
|
|
message="Hardcoded string "Género: --", should use `@string` resource"
|
|
category="Internationalization"
|
|
priority="5"
|
|
summary="Hardcoded text"
|
|
explanation="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."
|
|
errorLine1=" android:text="Género: --""
|
|
errorLine2=" ~~~~~~~~~~~~~~~~~~~~~~~~~">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/src/main/res/layout/activity_main.xml"
|
|
line="344"
|
|
column="25"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="HardcodedText"
|
|
severity="Warning"
|
|
message="Hardcoded string "Horário: --", should use `@string` resource"
|
|
category="Internationalization"
|
|
priority="5"
|
|
summary="Hardcoded text"
|
|
explanation="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."
|
|
errorLine1=" android:text="Horário: --""
|
|
errorLine2=" ~~~~~~~~~~~~~~~~~~~~~~~~~~">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/src/main/res/layout/activity_main.xml"
|
|
line="353"
|
|
column="25"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="HardcodedText"
|
|
severity="Warning"
|
|
message="Hardcoded string "EDITAR DADOS", should use `@string` resource"
|
|
category="Internationalization"
|
|
priority="5"
|
|
summary="Hardcoded text"
|
|
explanation="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."
|
|
errorLine1=" android:text="EDITAR DADOS""
|
|
errorLine2=" ~~~~~~~~~~~~~~~~~~~~~~~~~~~">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/src/main/res/layout/activity_main.xml"
|
|
line="363"
|
|
column="17"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="HardcodedText"
|
|
severity="Warning"
|
|
message="Hardcoded string "TERMINAR SESSÃO", should use `@string` resource"
|
|
category="Internationalization"
|
|
priority="5"
|
|
summary="Hardcoded text"
|
|
explanation="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."
|
|
errorLine1=" android:text="TERMINAR SESSÃO""
|
|
errorLine2=" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/src/main/res/layout/activity_main.xml"
|
|
line="375"
|
|
column="17"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="HardcodedText"
|
|
severity="Warning"
|
|
message="Hardcoded string "Especialidade", should use `@string` resource"
|
|
category="Internationalization"
|
|
priority="5"
|
|
summary="Hardcoded text"
|
|
explanation="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."
|
|
errorLine1=" android:hint="Especialidade""
|
|
errorLine2=" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/src/main/res/layout/activity_register.xml"
|
|
line="71"
|
|
column="25"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="HardcodedText"
|
|
severity="Warning"
|
|
message="Hardcoded string "Sexo", should use `@string` resource"
|
|
category="Internationalization"
|
|
priority="5"
|
|
summary="Hardcoded text"
|
|
explanation="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."
|
|
errorLine1=" android:hint="Sexo">"
|
|
errorLine2=" ~~~~~~~~~~~~~~~~~~~">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/src/main/res/layout/activity_register.xml"
|
|
line="82"
|
|
column="21"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="HardcodedText"
|
|
severity="Warning"
|
|
message="Hardcoded string "Alterar Palavra-passe", should use `@string` resource"
|
|
category="Internationalization"
|
|
priority="5"
|
|
summary="Hardcoded text"
|
|
explanation="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."
|
|
errorLine1=" android:text="Alterar Palavra-passe""
|
|
errorLine2=" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/src/main/res/layout/dialog_change_password.xml"
|
|
line="11"
|
|
column="9"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="HardcodedText"
|
|
severity="Warning"
|
|
message="Hardcoded string "Nova Palavra-passe", should use `@string` resource"
|
|
category="Internationalization"
|
|
priority="5"
|
|
summary="Hardcoded text"
|
|
explanation="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."
|
|
errorLine1=" android:hint="Nova Palavra-passe""
|
|
errorLine2=" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/src/main/res/layout/dialog_change_password.xml"
|
|
line="26"
|
|
column="13"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="HardcodedText"
|
|
severity="Warning"
|
|
message="Hardcoded string "Cancelar", should use `@string` resource"
|
|
category="Internationalization"
|
|
priority="5"
|
|
summary="Hardcoded text"
|
|
explanation="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."
|
|
errorLine1=" android:text="Cancelar""
|
|
errorLine2=" ~~~~~~~~~~~~~~~~~~~~~~~">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/src/main/res/layout/dialog_change_password.xml"
|
|
line="43"
|
|
column="13"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="HardcodedText"
|
|
severity="Warning"
|
|
message="Hardcoded string "Salvar", should use `@string` resource"
|
|
category="Internationalization"
|
|
priority="5"
|
|
summary="Hardcoded text"
|
|
explanation="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."
|
|
errorLine1=" android:text="Salvar" />"
|
|
errorLine2=" ~~~~~~~~~~~~~~~~~~~~~">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/src/main/res/layout/dialog_change_password.xml"
|
|
line="50"
|
|
column="13"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="HardcodedText"
|
|
severity="Warning"
|
|
message="Hardcoded string "Foto do utente", should use `@string` resource"
|
|
category="Internationalization"
|
|
priority="5"
|
|
summary="Hardcoded text"
|
|
explanation="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."
|
|
errorLine1=" android:contentDescription="Foto do utente""
|
|
errorLine2=" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/src/main/res/layout/item_consulta_medico.xml"
|
|
line="33"
|
|
column="17"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="HardcodedText"
|
|
severity="Warning"
|
|
message="Hardcoded string "Nome do Paciente", should use `@string` resource"
|
|
category="Internationalization"
|
|
priority="5"
|
|
summary="Hardcoded text"
|
|
explanation="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."
|
|
errorLine1=" android:text="Nome do Paciente""
|
|
errorLine2=" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/src/main/res/layout/item_consulta_medico.xml"
|
|
line="46"
|
|
column="21"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="HardcodedText"
|
|
severity="Warning"
|
|
message="Hardcoded string "Data e Hora", should use `@string` resource"
|
|
category="Internationalization"
|
|
priority="5"
|
|
summary="Hardcoded text"
|
|
explanation="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."
|
|
errorLine1=" android:text="Data e Hora""
|
|
errorLine2=" ~~~~~~~~~~~~~~~~~~~~~~~~~~">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/src/main/res/layout/item_consulta_medico.xml"
|
|
line="55"
|
|
column="21"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="HardcodedText"
|
|
severity="Warning"
|
|
message="Hardcoded string "Pendente", should use `@string` resource"
|
|
category="Internationalization"
|
|
priority="5"
|
|
summary="Hardcoded text"
|
|
explanation="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."
|
|
errorLine1=" android:text="Pendente""
|
|
errorLine2=" ~~~~~~~~~~~~~~~~~~~~~~~">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/src/main/res/layout/item_consulta_medico.xml"
|
|
line="64"
|
|
column="21"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="HardcodedText"
|
|
severity="Warning"
|
|
message="Hardcoded string "Rejeitar", should use `@string` resource"
|
|
category="Internationalization"
|
|
priority="5"
|
|
summary="Hardcoded text"
|
|
explanation="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."
|
|
errorLine1=" android:text="Rejeitar" />"
|
|
errorLine2=" ~~~~~~~~~~~~~~~~~~~~~~~">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/src/main/res/layout/item_consulta_medico.xml"
|
|
line="88"
|
|
column="17"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="HardcodedText"
|
|
severity="Warning"
|
|
message="Hardcoded string "Aceitar", should use `@string` resource"
|
|
category="Internationalization"
|
|
priority="5"
|
|
summary="Hardcoded text"
|
|
explanation="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."
|
|
errorLine1=" android:text="Aceitar" />"
|
|
errorLine2=" ~~~~~~~~~~~~~~~~~~~~~~">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/src/main/res/layout/item_consulta_medico.xml"
|
|
line="96"
|
|
column="17"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="HardcodedText"
|
|
severity="Warning"
|
|
message="Hardcoded string "Foto do paciente", should use `@string` resource"
|
|
category="Internationalization"
|
|
priority="5"
|
|
summary="Hardcoded text"
|
|
explanation="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."
|
|
errorLine1=" android:contentDescription="Foto do paciente""
|
|
errorLine2=" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/src/main/res/layout/item_paciente.xml"
|
|
line="29"
|
|
column="13"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="HardcodedText"
|
|
severity="Warning"
|
|
message="Hardcoded string "Nome do Paciente", should use `@string` resource"
|
|
category="Internationalization"
|
|
priority="5"
|
|
summary="Hardcoded text"
|
|
explanation="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."
|
|
errorLine1=" android:text="Nome do Paciente""
|
|
errorLine2=" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/src/main/res/layout/item_paciente.xml"
|
|
line="42"
|
|
column="17"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="HardcodedText"
|
|
severity="Warning"
|
|
message="Hardcoded string "email@exemplo.com", should use `@string` resource"
|
|
category="Internationalization"
|
|
priority="5"
|
|
summary="Hardcoded text"
|
|
explanation="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."
|
|
errorLine1=" android:text="email@exemplo.com""
|
|
errorLine2=" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/src/main/res/layout/item_paciente.xml"
|
|
line="51"
|
|
column="17"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="HardcodedText"
|
|
severity="Warning"
|
|
message="Hardcoded string "Pacientes", should use `@string` resource"
|
|
category="Internationalization"
|
|
priority="5"
|
|
summary="Hardcoded text"
|
|
explanation="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."
|
|
errorLine1=" android:title="Pacientes" />"
|
|
errorLine2=" ~~~~~~~~~~~~~~~~~~~~~~~~~">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/src/main/res/menu/menu_bottom.xml"
|
|
line="6"
|
|
column="9"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="HardcodedText"
|
|
severity="Warning"
|
|
message="Hardcoded string "Agenda", should use `@string` resource"
|
|
category="Internationalization"
|
|
priority="5"
|
|
summary="Hardcoded text"
|
|
explanation="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."
|
|
errorLine1=" android:title="Agenda" />"
|
|
errorLine2=" ~~~~~~~~~~~~~~~~~~~~~~">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/src/main/res/menu/menu_bottom.xml"
|
|
line="10"
|
|
column="9"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="HardcodedText"
|
|
severity="Warning"
|
|
message="Hardcoded string "Consultas", should use `@string` resource"
|
|
category="Internationalization"
|
|
priority="5"
|
|
summary="Hardcoded text"
|
|
explanation="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."
|
|
errorLine1=" android:title="Consultas" />"
|
|
errorLine2=" ~~~~~~~~~~~~~~~~~~~~~~~~~">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/src/main/res/menu/menu_bottom.xml"
|
|
line="14"
|
|
column="9"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="HardcodedText"
|
|
severity="Warning"
|
|
message="Hardcoded string "Perfil", should use `@string` resource"
|
|
category="Internationalization"
|
|
priority="5"
|
|
summary="Hardcoded text"
|
|
explanation="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."
|
|
errorLine1=" android:title="Perfil" />"
|
|
errorLine2=" ~~~~~~~~~~~~~~~~~~~~~~">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/src/main/res/menu/menu_bottom.xml"
|
|
line="18"
|
|
column="9"/>
|
|
</issue>
|
|
|
|
</issues>
|