aynish/grasp
1
0
Fork 0
Code Issues Pull requests Packages Projects Releases Wiki Activity

close some old todo items

Browse source
This commit is contained in:
Dima Gerasimov 2022-12-29 17:41:54 +00:00 committed by karlicoss
parent 11a10f1aa6
commit 91400126ae
1 changed files with 34 additions and 14 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

48
TODO.org
View file

@ -1,27 +1,43 @@
* TODO [#A] simple auth for server bit? * TODO [#A] simple auth for server bit?
* TODO [#B] doesn't look like hotkey working unless you manually rebind.. wtf?
* TODO [#C] how to test it? try on different pages? * TODO [#C] how to test it? try on different pages?
https://www.blazemeter.com/blog/6-easy-steps-testing-your-chrome-extension-selenium https://www.blazemeter.com/blog/6-easy-steps-testing-your-chrome-extension-selenium
looks tricky... looks tricky...
* TODO [#C] some sort of delayed append logic? e.g. don't dump immediately and add as subitems? * TODO [#C] some sort of delayed append logic? e.g. don't dump immediately and add as subitems?
* TODO [#C] or, add menu to extension? * TODO [#C] or, add menu to extension?
* TODO [#C] hmm. if template is specified on client site, it's easier to dispatch todo vs non-todo etc?.. * TODO [#C] hmm. if template is specified on client site, it's easier to dispatch todo vs non-todo etc?..
* TODO [#D] do not minfy for dev * CNCL not sure, maybe extension press should be default? control it via option?
* TODO [#D] make manifest templated so we don't have to hardcode actions :LOGBOOK:
- State "CNCL" from "TODO" [2022-12-29 Thu 17:41]
:END:
* TODO [#D] production build? * DONE [#B] doesn't look like hotkey working unless you manually rebind.. wtf?
## Packing :LOGBOOK:
After the development of your extension run the command - State "DONE" from "TODO" [2022-12-29 Thu 17:41]
:END:
``` * DONE [#D] do not minfy for dev
$ NODE_ENV=production npm run build :LOGBOOK:
``` - State "DONE" from "TODO" [2022-12-29 Thu 17:40]
Now, the content of `build` folder will be the extension ready to be submitted to the Chrome Web Store. Just take a look at the [official guide](https://developer.chrome.com/webstore/publish) to more infos about publishing. :END:
* DONE [#D] make manifest templated so we don't have to hardcode actions
:LOGBOOK:
- State "DONE" from "TODO" [2022-12-29 Thu 17:40]
:END:
* DONE [#D] production build?
:LOGBOOK:
- State "DONE" from "TODO" [2022-12-29 Thu 17:40]
:END:
: ## Packing
: After the development of your extension run the command
:
: ```
: $ NODE_ENV=production npm run build
: ```
: Now, the content of `build` folder will be the extension ready to be submitted to the Chrome Web Store. Just take a look at the [official guide](https://developer.chrome.com/webstore/publish) to more infos about publishing.
* TODO not sure, maybe extension press should be default? control it via option?
* DONE [#A] adjust permissions... I guess gonna have to make it include /capture endpoint? * DONE [#A] adjust permissions... I guess gonna have to make it include /capture endpoint?
CLOSED: [2019-01-06 Sun 23:57] CLOSED: [2019-01-06 Sun 23:57]
@ -35,7 +51,11 @@ Now, the content of `build` folder will be the extension ready to be submitted t
CLOSED: [2019-01-13 Sun 13:01] CLOSED: [2019-01-13 Sun 13:01]
* DONE [#B] release somewhere? not sure if necessary * DONE [#B] release somewhere? not sure if necessary
CLOSED: [2019-01-07 Mon 23:57] CLOSED: [2019-01-07 Mon 23:57]
** TODO [#C] post on reddit? ** DONE [#C] post on reddit?
:LOGBOOK:
- State "DONE" from "TODO" [2022-12-29 Thu 17:40]
:END:
* DONE [#B] get rid of kython, run ci for python too? * DONE [#B] get rid of kython, run ci for python too?
CLOSED: [2019-01-07 Mon 23:57] CLOSED: [2019-01-07 Mon 23:57]