Closed dustinvtran closed 2 years ago
We could do something like:
This is the UX I've gone with, I think it doesn't have any drawback but is a lot simpler. Let me know if you need something else.
I like it! It is indeed much simpler. Bug-related (and not UI-related), I'm seeing:
Fixed by: f455955c3652c1adcd2abffcc4fdcf048fddfa26 ffdc7cc60d338f5830d1cacc6cbd07ca4f915be3
Re-open if still occurring.
This makes it easier to trace changes when we want to periodically update the database data in the future. For users, we'll want to preserve their edits but having, e.g., the diff of the database data alongside their edits as separate fields lets them know when they can just remove their manually edited fields.
Example. You manually update an entry's year from tba to 2022. Later the database updates the year properly. Now you can remove that year addition as it appears in the database's default fields.