search

status-im / pluto

https://status-im.github.io/pluto/
12 stars 3 forks source link

[Request] Improve development process for extensions #110

Open rachelhamlin opened 5 years ago

rachelhamlin commented 5 years ago

Extensions are also a PITA to iterate on. Almost masochistic.

Quote from Tom's submission to our ETHSingapore prize.

Per Andrey, for bigger extensions we need a way to develop locally.

morelazers commented 5 years ago

One of the main ideas I had is the ability to log vars in the editor by connecting to a specific instance of the Status app.

Something like a specific "dev" QR code which enables the app instance to expose extension variables over WebSocket or something similar to the web editor, so they can then be inspected. It would be even more extra neato if this connection allowed us to perform extension queries by interacting with the web interface, with the results printed in-browser, allowing the inspection of data structures.

For someone who is new to Clojure syntax this would make getting to grips with it a lot easier, and would also pair well with development of the /extensions/core.cljs file to expose new queries/events to extension developers.

This would really help people inspect their extensions and I don't think it's a huge leap in terms of what's possible if I understand the app's architecture correctly.

I sent something like this to @jeluard a while ago but posting here for longevity.

rachelhamlin commented 5 years ago

Very nice. Thanks for capturing, @morelazers.