Hi! Been there, thought that. This point is a bit of a pain for me too, because for example whenever you publish a list of texts (product name) or numbers (a quantity) to Bubble it cannot contain duplicates. This makes any easy JS handling useless. UnlessâŚ
Iâve been thinking of using offline in-browser database management systems like http://hood.ie/ or just https://pouchdb.com/ for more complex stuff (probably not needed in this case!), however thereâs the limitation when dealing with Bubbleâs native lists.
I havenât really tinkered with it yet (itâs on my âsomedayâ list), however I think that if we can get to pass an encoded string containing the values (objects) as a Bubble native single text (not a list, just a string) and at the workflow level have a decoding action that is able to get that single string/text and output objects one by one on a self scheduling (looping) scheduled workflow action⌠we could have an efficient way to handle it even server side (within Bubbleâs app).
The same solution would be able to, when working with elements and displaying stuff for the users on the front side, publish a single string to several Bubble elements and having each of these elements decoding it depending on their cell index. Or something else like that. That solution would be infinitely scalable.
I know that this feels a bit different from just publishing a list to Bubble, but Iâm saying this because we just canât publish a list of quantities, Bubble would eat (remove) any values that are not unique and we would end up with an incomplete list.
However, if youâre not having too many items, you could just have a plugin element with, say, 60 states and publish to all of them individually, being 20 states âitem ID Xâ, another 20 âitem name Xâ and the remaining 20 âitem quantity Xâ, with X being the index position of the item, and get the data sources of the elements in the repeating group to listen to the states with an index equaling to their cell index. But letâs not get started on the hassle that maintaining this would be.
These are possible ways for us to do client side experiences like a shopping cart that works instantly (and for free in terms of app capacity) by not needing to touch the database for non unique values.
Phew.