abulvenz
abulvenz
@masenf I just encountered it again (see below). Even with the workaround (hopefully applied correctly (I'm not a react-expert)) it doesn't work (OK, the error is gone, but the click...
Sometimes you need multiple boxes. :mechanic: ```python rx.dialog.trigger( rx.box( rx.tooltip( rx.box(button), content=action.name, ) ) ), ``` It feels like in sokoban. :smile:
> > Then `` can work as a child of the tooltip. > > I wonder if it makes sense to eventually structure all of the memoized components in this...
@masenf In their documentation they write it is best practice to always use forwardRef ```Whilst this isn't necessary for all parts, we recommend always doing it so that you are...
Nobody wants to do a red2green :adhesive_bandage: with given tests? What's up :smiley_cat: ? It's like a task from advent of code.
OK, I see. Sorry that I didn't do the history digging :+1: Thanks!
> to be clear, i still think `State.setvar("object.name")` is sweet! we should keep that. Ah, sorry, tiny misunderstanding :smile: , so we are still in the game :game_die: . With...
> closing this due to inactivity, feels free to resurrect it when appropriate 👍 Thanks for closing it for me. FMPOV it lost its charm when making it string-based again...
Yes, I can confirm this.
Thanks for the fast reply @masenf . We have implemented the last workaround and yield the entire object as `None` and yield the new value afterwards. It causes a tiny...