Should have Zapier-webhook ID stored in indexedDB

eklem / nowcontent.xyz

Create bookmarklets for sending content / pages to service [xyz]

MIT License

7 stars 1 forks source link

Should have Zapier-webhook ID stored in indexedDB #29

Closed eklem closed 5 years ago

eklem commented 5 years ago

Then it can be universally used, and no problem with people sharing secret keys.

eklem commented 5 years ago

Check if key/value with Zapier webhook is set in indexedDB, if so, update href for bookmarklet, show button with link and hide form for inserting Zapier link

eklem commented 5 years ago

Use Dexie.js to handle indexedDB

eklem commented 5 years ago

Store the following

[x] webhook url
[x] button & bookmark text (the text for the href)

The last part is to open up for having several search engines in nowsearch.xyz. Should be optional.

eklem commented 5 years ago

Check out Sanity.io for later use.

eklem commented 5 years ago

Will most probably work with Sanity.io through the http api. Need three info nuggets:

[x] project-id
[x] dataset-name
[x] tokenWithWriteAccess

eklem commented 5 years ago

Just use localstorage for now: https://codepen.io/cfjedimaster/pen/KodaKb

eklem commented 5 years ago

Closer now, so keeping the indexedDB approach. Check the promise-example to get further: https://dexie.org/docs/Tutorial/Getting-started

eklem commented 5 years ago

Now able to add a stringified object to a content-field. Can pick up each table row with [where key equals...](https://dexie.org/docs/WhereClause/WhereClause.equals())

eklem commented 5 years ago

This is the way to go. Will make it easy to combine a lot of different services in one key/value table.

eklem commented 5 years ago

Storing stuff like no tomorrow.