Open mrvivacious opened 2 years ago
User can save their hourly rate to storage. The Hourly Rate field in the popup also displays that rate when the value is present in storage.
Before 1.0 release, we want a data schema for the user to make data interfacing easier. Additionally, having a schema now will circumvent needing to create a data standardization + migration if we ever decided that our current implementation isn't enough*
* = Yes, even with a schema now we may still decide someday that our interface could use some tweaks, but it's easier to add and remove values from an existing dictionary / object than it is to grab a bunch of strings, put them all into an object, then delete the strings and add the necessary code to make sure the UI grabs from the object. Yes, both aren't difficult in nature, but the first stragey is just easier, ok?
As a user I want my data synced to my account So that if I switch computers, I can pick up where I left off with this tool.
Acceptance criteria: Data schema is planned on the pretense that any references / interactions with data storage/retrieval use chrome.storage.sync.
Work description: Figure out what data we would want to save (example) and what the schema looks like (ie. JSON object? Individual key value pairs?). Use chrome.storage.sync instead of local storage. A sample line for where to make this switch.