You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
create a build process for generating bookmarkletes that function in the same way as the extension, with user predefined config and storage values
come up with a better logo (how about a seppukucat with a katana and a man bun?)
design a better and more universal SimpleStorage class.
currently, your storage api and techniques might be a bit finicky given their blackbox-like handling of first-time assignments/empty storage entries.
a lot of the first-time values are assined by the option.ts script. and it shouldn't be like that since option.ts should ideally deal only with the ui of option.html.
setup a default-value system and link it to the "reset" button in the options.html page.
this one won't work, because window.localStorage can only store Record<string, string>, whereas our schema has arrays and objects as values inside of it.
I could encode the values as json when "setting", and parse that json back when "getting", but that's for later.
temporary map/object storage , so that it can work across different environments, including bookmarklets
Take care of the following tasks before hitting
v0.2.0add option to choose if one wishes to strictly adhere to REST api in incognito mode, along with no authentication key
add feature for downloading files and folders in a single ".tar.gz" archive file
create a build process for generating bookmarkletes that function in the same way as the extension, with user predefined
configandstoragevaluescome up with a better logo (how about a seppukucat with a katana and a man bun?)
design a better and more universal
SimpleStorageclass.currently, your storage api and techniques might be a bit finicky given their blackbox-like handling of first-time assignments/empty storage entries.
a lot of the first-time values are assined by the
option.tsscript. and it shouldn't be like that sinceoption.tsshould ideally deal only with the ui ofoption.html.options.htmlpage.window.localStoragecan only storeRecord<string, string>, whereas our schema has arrays and objects as values inside of it.I could encode the values as json when "setting", and parse that json back when "getting", but that's for later.