search

cioraneanu / firefly-pico

A delightful Firefly III companion web app for effortless transaction tracking
GNU Affero General Public License v3.0
183 stars 5 forks source link

[Suggestion] Persist settings in database #31

Open avee87 opened 3 weeks ago

avee87 commented 3 weeks ago

Currently they live in local storage which means they are not shared across devices. As the number of settings grows it becomes increasingly easy for them to go out of sync. Also if you ever clear local data in your browser you lose everything.

I would argue that only connection settings should live in local storage and the rest should be persisted.

cioraneanu commented 3 weeks ago

Persisting in DB would indeed have benefits but those settings need to be associated with an user. For example me and my wife both share the same Firefly acount but she has her own settings (ex.New transaction defaults). Creating separate login accounts(registration, account managent etc) for both Firefly and Pico don't seem like a great choice.

One possible solution would be to create "profiles" and anyone with a valid Personal Token can choose which one to use. Thoughts? 🤔

avee87 commented 3 weeks ago

Profile per token sounds like a great solution!