mtamc / memo

Website for rating books, movies, video games, and TV shows.
0 stars 0 forks source link

Make explicit in the "Edit an entry" UI when user has overwritten the database fields #9

Closed dustinvtran closed 2 years ago

dustinvtran commented 2 years ago

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.

dustinvtran commented 2 years ago

We could do something like:

  1. There are two columns (like it is currently): column 1 for database info and column 2 for user info.
  2. The first column's fields are displayed in greyed-out text boxes.
  3. There's an "Edit" button next to each greyed-out text box. Clicking on it adds a white text box above the greyed-out text box. The white text box is editable and will be the one displayed in the tables.
  4. There's a "Delete" button next to each white text box. Clicking on it removes the manual field so the entry will now just display info from the greyed-out text box.
ghost commented 2 years ago

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.

1644081903

dustinvtran commented 2 years ago

I like it! It is indeed much simpler. Bug-related (and not UI-related), I'm seeing:

ghost commented 2 years ago

Fixed by: f455955c3652c1adcd2abffcc4fdcf048fddfa26 ffdc7cc60d338f5830d1cacc6cbd07ca4f915be3

Re-open if still occurring.