Skip to content

Add configurable save directory for Autofill-saved entries - #1035

Open
AuthenticSm1les wants to merge 1 commit into
agrahn:developfrom
AuthenticSm1les:feature/save-root-directory-agrahn
Open

Add configurable save directory for Autofill-saved entries#1035
AuthenticSm1les wants to merge 1 commit into
agrahn:developfrom
AuthenticSm1les:feature/save-root-directory-agrahn

Conversation

@AuthenticSm1les

Copy link
Copy Markdown

Summary

  • Credentials saved via the Autofill framework (the system "Save to Password Store?" prompt, shown while the app is closed) are always written directly to the repository root, with no way to route them into a category subfolder.
  • Adds a "Save directory" setting under Settings > Autofill (AutofillPreferences.saveDirectory()) that lets users specify a root subfolder (e.g. www); Autofill-originated saves are then resolved under that folder instead of the store root.
  • Scoped entirely to the Autofill save path (AutofillSaveActivity) — leaving it unset preserves existing behavior exactly, and the in-app "+" entry creation flow is unaffected in every case.

Test plan

  • ./gradlew :app:compileDebugKotlin — builds clean against develop
  • Manual: set "Save directory" to www, trigger an Autofill save prompt on a new site, confirm the entry lands at www/<site>/<file> instead of the store root
  • Manual: leave "Save directory" empty, confirm Autofill saves still land at the store root as before

Credentials saved via the Autofill framework (the system "Save to
Password Store?" prompt shown while the app is closed) were always
written directly to the repository root, with no way to route them
into a category subfolder like a user-organized store might use.

Add a "Save directory" setting under Settings > Autofill that lets
users specify a root subfolder; Autofill-originated saves are then
resolved under that folder instead of the store root. Leaving it
unset preserves the existing behavior exactly. The in-app "+" entry
creation flow is unaffected in every case.

Fixes pando85#127
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