saving an editor/canvas state is too complex man. one way is to have a db call on each meaningful action, easy to build but causes too much db calls.
another way is to have a reconciliation strategy with a debounce save timer.
- is very efficient comparatively
- much better UX.
๐๐ช๐ต๐ฒ๐๐ต๐ฒ๐ฟ ๐๐ผ๐ ๐ฎ๐ฟ๐ฒ ๐ฎ ๐ป๐ฒ๐ ๐ฐ๐ผ๐ป๐๐ฟ๐ถ๐ฏ๐๐๐ผ๐ฟ ๐ผ๐ฟ ๐ฝ๐ฟ๐ฒ๐ฝ๐ฎ๐ฟ๐ถ๐ป๐ด ๐ณ๐ผ๐ฟ ๐๐ฆ๐ผ๐/๐๐๐ซ/๐ฆ๐ข๐'๐ฎ๐ณ
I don't think it will take time to grab the ultimate guide with experience for open source.
https://t.co/o1MVRQBzxB
building softwares is way different these days than it used to be. have seen founders writing code with speed and compromising reliability.
main goal has become to write code fast with AI and just to make it work today...
building my own n8n these days, have a similar feature there.
right now have gone with B, encrypt the user key after testing it for validation and stored the encrypted key.
BYOK for each request sounds very hassle. one good way to ensure trust is to give keys usage logs to user.
added config panel for each node, the ui looks off, will improve later...
right now the main challenge while building this is handelling the save part. you have to save the workflow, state, data configured for each node (config panel), position of each node.
after all this, the config fields for each node, could be dynamic too...
๐๐ผ๐ฟ ๐๐ต๐ฒ ๐ฝ๐ฒ๐ผ๐ฝ๐น๐ฒ ๐๐ต๐ผ ๐๐ฎ๐ป๐๐ ๐๐ผ ๐ด๐ฒ๐ ๐๐ผ๐บ๐ฒ ๐ด๐๐ถ๐ฑ๐ฎ๐ป๐ฐ๐ฒ ๐ฎ๐ฏ๐ผ๐๐ ๐ข๐ฆ๐ฆ/๐๐ฆ๐ผ๐'๐ฎ๐ณ
Imagine an open-source community so goated that almost 750+ people are waiting to get in !!
Here's our discord - https://t.co/GxEmoDpZot