Love when my favorite Bubbler drops. I've also been CRUD-ifying workflows into a reusable element. In reading the newest Bubble docs on the native editor, seems like a lot of new assets will have to be made to port over with the new Stacks, Views system replacing web pages. I would love to see you fulfill the rest of CRUD, then execute realtime. When it comes to CRUD I am confused personally when to mark custom events as 'create' vs. 'update', especially in event based workflows (polling like you said, LLM streaming, etc.). Also been trying to figure out when to make double custom event loops for each thing vs a extract to text then a. :split by action. When viewing/gathering a set of data for use (such as setting messages up for a prompt/getting response embeddings), when do you think it makes more sense to cache data in a state/page element so its ready to be referenced faster than looping through every individual thing in a list right at a user action?
A lot of questions in this one and no easy answers unfortunately. The easy answer is. It depends.. Personally, I think with the new if/else & parallel execution & loops. A lot of paradigms we were used to may be changing/improving for ease. So I'm hesitant to suggest any practises that will essentially be out of date in hopefully 3 months when all this exciting stuff comes out
First 🥇😅
Congratulations on the content 🤝
Love when my favorite Bubbler drops.
I've also been CRUD-ifying workflows into a reusable element. In reading the newest Bubble docs on the native editor, seems like a lot of new assets will have to be made to port over with the new Stacks, Views system replacing web pages.
I would love to see you fulfill the rest of CRUD, then execute realtime. When it comes to CRUD I am confused personally when to mark custom events as 'create' vs. 'update', especially in event based workflows (polling like you said, LLM streaming, etc.).
Also been trying to figure out when to make double custom event loops for each thing vs a extract to text then a. :split by action.
When viewing/gathering a set of data for use (such as setting messages up for a prompt/getting response embeddings), when do you think it makes more sense to cache data in a state/page element so its ready to be referenced faster than looping through every individual thing in a list right at a user action?
A lot of questions in this one and no easy answers unfortunately.
The easy answer is. It depends..
Personally, I think with the new if/else & parallel execution & loops. A lot of paradigms we were used to may be changing/improving for ease.
So I'm hesitant to suggest any practises that will essentially be out of date in hopefully 3 months when all this exciting stuff comes out