Thanks for sharing, noted this as a feature request, so we can consider this in our future product roadmap and feel free to add these ideas to our Ideaboard, so other users can upvote them!
Hmmm hate to be the negative Nancy but Iâm sure everyone would have preferred this time spent on the PDF plug-in, maintaining the bubble plugins or something more useful than making things more confusing for people who werenât confused to start off with
In my experience, newer Bubble users donât know to hover the dynamic expression to see the evaluator. It actually took me a couple of years to randomly see it.
I believe Bubbleâs goals are to become more intuitive and user friendly for newer Bubblers to increase the user base. I personally think this will make it so.
I also feel confident enough at this stage in my use of Bubble to not be overwhelmed by the change and that Iâd be able to read through the expression just as easily as if it werenât there.
And to be completely honest, About 2 weeks ago I made a comment to a Bootcamp session that I wish Bubble made it easier to know if the data field I created that is a list was a list while putting together a dynamic expression. Maybe Big Brother is listening
Precisely why I include it in my training material; although as I mentioned in this thread, I suspect most users do actually trigger it (itâs hard not to) but simply donât ânoticeâ what itâs telling them (hence the reason for my recommendations regarding its appearance).
Also, FWIW, this feature was introduced about 2.5 years ago, so it hasnât been around since Bubbleâs inception. Even long-time users might be âoverlookingâ it.
Just a little education and awareness raising are all thatâs needed IMOâ not a language change.
Hey everyone,
Sending a quick update! We heard your feedback and made some small changes outlined below.
-
We have hidden
:each item:converted to list
as this operator is a bit repetitive if youâre using it on a list of things. If youâre using:converted to list
on existing dynamic expressions, the operator will still appear and work properly in the dynamic expression, but it wonât show on the dropdown.:converted to list
will still appear if youâre using it forSingle Option:converted to list
, but it wonât appear forAll Options:converted to list
sinceAll Options
is already a list. -
For readability, we now show
:each item
in the dynamic expression only the first time itâs relevant. If:each item
applies immediately in following list operators, it will not be shown in the dynamic expression.
We hope that these modifications make the language change informative but less intrusive!
This has to be the biggest pet peeve I have with the bubble language. Would love an explanation on how âisnât liveâ came about.
Isnât it the truth?
Thank you so much for taking the feedback to heart. The changes are definitely an improvement.
I have another request that I think would be a further refinement. It seems to me that the word âitemâ isnât really needed. What about simply each Creator, each Slug, etc? And for lists, where it doesnât âread wellâ, simply add a âList ofâ prefix; so it would read each List of Tags, each List of Likes, etc.
These recommendations would, in my view:
- Visually simplify the menu listing further by eliminating a superfluous word.
- Convey the same meaning with fewer words and less redundancy.
- Be consistent with the âtype tipsâ that appear when hovering an expression.
- Result in fewer trips to my therapist to treat my Bubble-induced OCD.
What do you think, @grace.hong?
-Steve
The original âis not not not liveâ was to complex. So they simplified it.