Open M-Nicholls opened 3 years ago
Hi Miles,
So everytime when admin
I will ask for a reason and save as an update record in database.
You know there is a save button for each filter instead of a save button for all changes. So if admin needs to update 2 filters, he clicks 2 saves and input 2 comments and thus 2 records in history. Though ideally these 2 updates are in 1 operation and then should have 1 record/comment in history. -- if you're happy with this then I'll go ahead to do coding.
I need to think about this some more - we don't want to have to track changes for a profile that's being worked on, only for those currently in production. May need a "published" status.
Possible solution - add git to the directory containing the JSON profiles and do a nightly push.
profile information to include last update date and what the update was
add to admin - record last update update date/time and comment if a profile is saved record the lat update date/time and prompt for a description all change history to be kept
add to profile info dialogue - only show last update date/time, update comment have an expandable show update history section