Skip to content

🧹 Sentinel: Remove unused persist_floating_keyboard - #719

Open
LeanBitLab wants to merge 1 commit into
mainfrom
sentinel/remove-persist-floating-keyboard-10788860027012443306
Open

LeanBitLab wants to merge 1 commit into
mainfrom
sentinel/remove-persist-floating-keyboard-10788860027012443306

Conversation

@LeanBitLab

Copy link
Copy Markdown
Owner

💡 What:
Removed the PREF_PERSIST_FLOATING_KEYBOARD preference, property mPersistFloatingKeyboard, and the persist_floating_keyboard strings across all locale values. The feature was deprecated and the related property was hardcoded to false and being cleaned up in SettingsValues.kt.

🔍 Verification:
Searched the repository via grep to verify zero remaining references to persist_floating_keyboard strings and properties. Ran ./gradlew :app:assembleStandardDebug and ./gradlew :app:testStandardDebugUnitTest with no errors.

📦 Impact:
Reduces technical debt, cleans up obsolete strings saving space, and removes dead SharedPreferences cleanup logic from the Settings flow.


PR created automatically by Jules for task 10788860027012443306 started by @LeanBitLab

…d`. Here is a summary of the changes:

💡 **What:**
I removed the `PREF_PERSIST_FLOATING_KEYBOARD` preference, the `mPersistFloatingKeyboard` property, and the `persist_floating_keyboard` strings across all locale values. The feature was deprecated, and the related property was hardcoded to false and being cleaned up in SettingsValues.kt.

🔍 **Verification:**
I searched the repository to verify there are zero remaining references to the `persist_floating_keyboard` strings and properties. I also ran `./gradlew :app:assembleStandardDebug` and `./gradlew :app:testStandardDebugUnitTest`, and both completed with no errors.

📦 **Impact:**
This reduces technical debt, cleans up obsolete strings to save space, and removes dead SharedPreferences cleanup logic from the Settings flow.
@google-labs-jules

Copy link
Copy Markdown

👋 Jules, reporting for duty! I'm here to lend a hand with this pull request.

When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down.

I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job!

For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with @jules. You can find this option in the Pull Request section of your global Jules UI settings. You can always switch back!

New to Jules? Learn more at jules.google/docs.


For security, I will only act on instructions from the user who triggered this task.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant