七麦数据

Bug fixes and performance improvements

- Fixes an issue where the app may request write access even after being granted it.
- Fixes an issue where transaction templates would not reflect the settings they were created with (fire immediately, flag, etc.).

- Fixes an issue where transaction templates would not reflect the settings they were created with (fire immediately, flag, etc.).

Fixes:
- Fixes an issue with currency input for some currencies in the transaction template screens. Previously, currency input was constrained to too small an input length, but that constraint has been lifted and large amounts are better supported.

Changed:
- As part of the above fix, all currency input across the app is now the same. This applies primarily to frugal months and transaction templates, but will apply to any future inputs as well.
- Sub-transaction amount input for transaction templates is no longer done via a modal. Instead, input occurs directly on the transaction template screen for more rapid entry.

New:
- Introduces device syncing capabilities, allowing you to automatically back up your Lumy data and access it on other devices by linking your email address. Existing users will be prompted to link an email address but maintain the option to continue as a guest. Those who choose the "guest" option can continue using Lumy without linking an email, but are at risk of data loss in the event of a logout or uninstall (the same as before!). Now, users with a mobile device and tablet (or multiple mobile devices!) can easily use the same Lumy data across their devices.

Important Notes (please read!):
- This was a major architectural overhaul as this type of functionality wasn't planned from the beginning. Most obstacles were easily overcome, but one that was difficult was migrating the data itself. This resulted in a one-time need for existing users to manually back up their data before it being accessible. You should be prompted to do so as soon as you choose an authentication option (link an email or remain a guest). Once done, you never have to it again. If you aren't prompted, head over to the Settings tab and scroll down to "Backup Lumy data".
- Regarding _what_ data is synced: ONLY Lumy data is ever synced across devices. This means your spend trackers, category views, frugal months and transaction templates are synced, while all of your financial data fetched via YNAB remains on YNAB-servers _only_. This is both done to reduce redundancy (i.e. having copies of YNAB data and no single-source-of-truth), but also for your peace of mind.

Changed:
- A bit of UI freshening, as it's hard to do a major rewrite without sprucing some things up along the way.

Updates the calculation for spent amount in the Targets Health report such that categories with durations longer than the currently selected date range will show the average spent for the entire duration of the target, not the date range. This is helpful in cases where you're viewing a shorter date range than the target duration and within that date range you paid the full amount of that target. Previously, that would've skewed your target health to look unhealthy--now, (assuming you haven't actually overspent your target), the target will correctly be healthy. Categories with monthly targets or targets less than the currently selected date range will continue to show average monthly spending across the entire date range.

- Fixes an issue where the Target Health Report was not updating when changing budgets.
- The Choose Period bottom sheet now closes after a period is selected. This better conforms to how other bottom sheets behave in the app.

New:

- Adds the ability to quickly see over-spending for categories and category groups in the Budget Burndown. Previously, over-spending was not shown and a $0 remaining balance was shown instead.

Fixes:
- Ensures that changes to category group names are reflected immediately. This was previously not happening due to a YNAB API limitation, but we added a workaround to ensure a better user experience.
- Ensures the ordering of category groups and their categories matches what you see in YNAB. Previously, ordering in Lumy only matched that of YNAB until you changed the order in YNAB. This is because the YNAB API does not communicate ordering changes in delta requests, which Lumy makes use of. Now, categories are pulled fresh and so the ordering can be respected.
- Fixes an issue where transactions created via templates were always inflows, even if they were configured as outflows.

Introduces transaction templates, which will roll out slowly. Templates are a new (in beta!) premium feature that allow you to configure certain properties of common transactions and then tap a button to instantly create that transaction or fill out the remaining properties and then create the transaction. Please note that this is the first feature that _writes_ to your budget, and as such, will require you to provide write access before creating any transactions.

Note about the beta: Right now, for ease, templates are written to your settings. Logging out will delete them. Additionally, they may be deleted if breaking changes are introduced. We will do our best to avoid that though!

Some common use cases:

- You purchase the same thing at a vending machine at work every so often: You could create a "Candy bar" template that has the payee "Vending Machine", an amount of $1.99, a category of "Snacks", and an account "My Checking". Maybe even throw in a memo of "My favorite mid-day treat". If you set up the template to "fire immediately", you can simply tap the template from your Budget Tab to instantly create that transaction whenever you want.
- You tend to split a meal with friends at lunch:_You could create a template that has a split transaction configured, and only enter the amounts once you know them, categorizing your amount as "Dining Out" but the remainder as "Money I'm Owed".

There are a lot of other use cases I'm sure, and maybe ones that we don't yet support. We'd love your feedback on what we can add/change about this feature.

Allows for quicker modification of spend tracker names by pre-populating the name field with the existing name during modification. Previously the existing name was shown as a "hint" that could not be modified.