cedricvlt / streamlit-condition-tree Goto Github PK

Description

I'm experiencing an issue with the streamlit-condition-tree component in my Streamlit application where the component does not seem to update correctly with its configuration. Initially, the component displays a default "index in index" query string, and then it should update based on user interaction and configuration changes. However, this update does not seem to occur as expected.
Steps to Reproduce

• Initialize the streamlit-condition-tree component with a DataFrame configuration.
• Run the Streamlit application.
• Interact with the component or trigger an update.
• Observe that the component does not update as expected and remains at the default state.

Expected Behavior

Upon interaction or receiving new configuration data, the streamlit-condition-tree component should update and reflect the changes based on user input or updated configuration.

Current Behavior

The component initializes with a default "index in index" state but does not update as expected with user interactions or when provided with new configuration data.

Environment

Streamlit version: 1.28.2
streamlit-condition-tree version: 0.1.2
Browser version: Chrome Version 119.0.6045.159 (Official Build) (64-bit) / Firefox 119.0.1 (64-bit)
Operating System: Ubuntu 22.04.3 LTS

Additional Context and Observations

The debug logs show that the component is registered and the script reruns on interaction, but the component's state does not seem to update with the new configuration.
Initial tests with different configurations suggest that the issue might be related to how the component's state is managed in Streamlit's reactive framework.
I have tried various troubleshooting steps, including checking the component's initialization, ensuring correct configuration formats, and testing in different environments (local and deployed).

I really appreciate the functionality that streamlit-condition-tree brings to Streamlit applications, and I'm eager to resolve this issue. Any insights or suggestions from the community or maintainers would be incredibly helpful.

Thank you for your time and effort in developing and maintaining this useful component.