search

WeAreWizards / passopolis-extensions

Continuation of the extensions code for mitro
GNU General Public License v3.0
81 stars 14 forks source link

[devdocs] Avoid creating a new extension on each build in chrome / or other way to easily develop #46

Closed amenk closed 7 years ago

amenk commented 7 years ago
  1. load extension/result in chrome
  2. edit extension code
  3. call nix-build nix/build.nix -A chrome-extension
  4. extension is placed under a new folder, so I can not just reload it in chrome

Also a new extension ID is generated, so I have to login again and again and so on...

teh commented 7 years ago

This is a feature of the build process which ensures that the final output is clean and doesn't accidentally contain development artifacts which could introduce security issues etc. If you are developing local you could write a script that automates some of that for you.

If you have more time you could move some of the stuff in extensions/nix/chrome-extension.nix etc to either a Makefile or a bash script and then call that from within chrome-extension.nix for building a release, and locally for development.

Edit: thanks for the rename.

amenk commented 7 years ago

but how are you working during development? Always re-adding the extension?

amenk commented 7 years ago

And how can I avoid that a new extension ID is created?

teh commented 7 years ago

Pretty much though I have a shell script somewhere that I can't find right now. Extension development is optimized for a clean release instead of fast iteration ATM . See also #34 for a necessary step before doing any substantial work.

amenk commented 7 years ago

I think we also should have a way for fast iterations ... especially for working on #34 -- or this also dependent on #34 somehow?

amenk commented 7 years ago

It works with just copying to /tmp/chrome-extensions - added info the readme https://github.com/amenk/passopolis-extensions/blob/patch-2/README.md