Problems with IDOM_FEATURE_INDEX_AS_DEFAULT_KEY #607
Replies: 5 comments 25 replies
-
The issues with Conreq Issues observed on
|
Beta Was this translation helpful? Give feedback.
-
Created an issue #613 for this. |
Beta Was this translation helpful? Give feedback.
-
I've attempted using a list instead of the unpack operator for the debug tabs. The result was the VDOM dict being rendered as a string on the page. Is this an IDOM bug, or have I done the syntax wrong? Do I need to avoid constructing the list via unpack? # Relevant LOCs
[
*( # Debug tabs
sidebar_group(
websocket,
state,
set_state,
group,
top_tabs=config._homepage.debug_nav_tabs,
)
for group in nav_tabs
if group == "Debug" and websocket.scope["user"].is_staff and DEBUG
)
], The original LOC looked like this |
Beta Was this translation helpful? Give feedback.
-
This should be fixed shortly: #614 |
Beta Was this translation helpful? Give feedback.
-
Gonna paste this here before I have to go. The minimum reproducible example will need the following (and a little more) @component
def parent():
state, set_state = idom.hooks.use_state( ... )
return div( child_wrapper(state, set_state), key=str(uuid4()) )
@component
def child(state, set_state):
child_state, set_child_state = idom.hooks.use_state( ... )
...
return something()
def child_wrapper(state, set_state):
return my_component(state, set_state) Will need to add in some buttons within the parent to switch between multiple children as well. |
Beta Was this translation helpful? Give feedback.
-
Opening this as a discussion first since I'm unsure if this is specific to how Conreq is dynamically generating children.
It seems like
IDOM_FEATURE_INDEX_AS_DEFAULT_KEY
is functionally broken. Conreq's homepage frequently fails to render tab changes now.Beta Was this translation helpful? Give feedback.
All reactions